01
Create a Flux API key
In Flux, go to Settings and generate an API key with read and write scopes. This token authenticates n8n's HTTP requests to the Flux REST API. Store it securely in n8n's credentials manager.
// n8n + Flux
Self-hosted board automation.
Connect Flux to n8n via the REST API. Build automation workflows on your own infrastructure. HTTP Request nodes, full API access, no vendor lock-in.
02
Add an HTTP Request node
In your n8n workflow, add an HTTP Request node. Set the method, URL, and headers. Use the Flux API base URL with the endpoint path (e.g., /api/cards) and set the Authorization header to Bearer followed by your API key.
03
Configure request parameters
Map workflow data into the Flux API request body. For card creation, include boardId, columnId, and title. For updates, include the cardId, fields to change, and expectedVersion for concurrency safety.
04
Self-host and control your data
n8n can run on your own infrastructure. Your Flux API calls stay within your network if both Flux and n8n are self-hosted. No data passes through third-party automation servers.
01 Why use n8n instead of Zapier or Make?
+
n8n is open-source and self-hostable. If you run your own infrastructure and want full control over your automation data, n8n lets you keep everything in your network. It also has no per-task pricing for self-hosted instances.
02 Can n8n handle complex Flux workflows?
+
Yes. n8n supports branching, looping, error handling, and JavaScript code nodes. You can build workflows that read multiple boards, filter cards by label or due date, batch-update cards, and chain API calls with conditional logic.
03 Does n8n have a native Flux node?
+
n8n does not have a native Flux node. You use the HTTP Request node to call the Flux REST API directly. This gives you access to every endpoint. You can also create a custom n8n node if you want a reusable abstraction within your n8n instance.
// Own your automation
Self-hosted, fully yours.
Flux REST API + n8n. Automate boards on your own infrastructure.