Using a Parameter in n8n
How to make an n8n automation read the current value of a Floxer Parameter on every run — without anyone touching the workflow itself.
What you'll build
Example used throughout this article: a weekly sales report that gets emailed to whichever address is set in Floxer. If a client updates that address, the next run automatically picks up the new value — nobody needs to open the n8n workflow.
A Parameter in Floxer is a value the client is allowed to change themselves, without needing access to n8n. Think of an email address, a limit, or a block of text. For the automation to actually use that value, it has to fetch it from the Floxer API on every run.
This article walks through one concrete example: an automation called Weekly Sales Report, which emails last week's sales summary. The recipient's address is stored as a Parameter, so the client can change it themselves.
- The Automation already exists in Floxer and you can see its public ID at the top of the Automation page.
- You have access to the n8n environment that holds the workflow.
- You can generate an API token for the Automation, from its API tab in Floxer.
Create the Parameter
Open the Automation, go to its Parameters tab, and add a new Parameter. The key is the technical name you'll refer to from n8n, so keep it short and consistent.
| Label | Value | Visible to client |
|---|---|---|
| Report day report_day |
Monday |
Editable by Client |
| Sales notification email sales_notification_email |
sales@northwindretail.com |
Editable by Client |
Tip: always use snake_case keys. That way the name in Floxer and the expression you write in n8n are guaranteed to match.
Generate an API token
Open the Automation's API tab. It shows the exact endpoint this Automation exposes, and lets you generate a token scoped to it.
Copy this token now — you won't be able to see it again.
- ScopeThis Automation only
- Ability
parameters:read
Save the token right away. Floxer only shows it once. Store it as an n8n Credential — never paste it directly into a node or a note.
Add an HTTP Request node
Place this node at the start of the workflow, before whichever node needs the recipient's address. Point it at the endpoint from step 2, authenticated with the token as a Bearer header.
n8n's own screens change a little between versions — the fields above are the ones that matter for this step, wherever they sit in your version.
The Header Auth credential just needs one header:
Name: Authorization Value: Bearer flx_example_do_not_use_9f8a2c7b1d4e6f30ab5c
Use the value in the next node
In the Send Email node, don't type a fixed address into the To field — reference the Get Parameters node instead, and read effective.sales_notification_email from its output.
Done — the workflow now looks up the recipient on every run instead of having it hard-coded.
Test the workflow
Run the workflow once manually and inspect the Get Parameters node's output.
Correct address in the output? Activate the workflow. From now on, whenever the client changes the value in Floxer, the next run picks it up automatically — nothing to update in n8n.
Do I need to repeat this for every Parameter?
No. One call to /parameters returns every Parameter for that Automation. Need another one? Just read a different field from the same effective object, e.g. effective.report_day.
The HTTP Request node returns 401 Unauthorized.
The token is invalid, revoked, expired, or belongs to a different Automation than the one in the URL. Generate a fresh token from the Automation's API tab.
effective.sales_notification_email is missing from the response.
Either the Parameter doesn't exist yet, or the key in Floxer doesn't quite match the key in your expression. Keys are case-sensitive — double-check them on the Automation's Parameters tab.
Can the client change the value themselves?
Yes — that's the whole point. The client updates the value from the Floxer client portal, no n8n access required. The workflow picks up the new value the next time it runs.