n8n, ready to run.
The n8n integration keeps the routing with n8n and the judgment with Floowed. Your workflow moves the work; we read what arrived, chase what is missing, and decide what happens next.
What it does.
What Floowed reads from n8n
- Whatever a workflow sends in, as the start of a case
- Documents and links carried on the payload
- Fields from anything your workflow can already reach
What it writes back
- The decision and its reasoning, back to the workflow
- The outcome, on to whatever the workflow does next
- A callback when a case that was waiting finally clears
Two things make n8n the better bridge for this work. Self-hosting keeps your case data and your credentials on your own infrastructure, which is the half of the privacy claim that actually holds: n8n's own telemetry never carries execution data, credentials or node parameters, though it does report workflow shape unless you turn it off. And unlike most bridges, an n8n workflow really can pause and resume: the Wait node hands out a resume URL, so one workflow can wait days for a decision rather than needing a second one to catch it.
An employee onboarding case, from signed offer to first day.
- Gather
A candidate is marked hired in Greenhouse. Your n8n workflow posts the hire to Floowed with a resume URL, and waits.
- Interpret
We read the signed offer, the ID and the right-to-work documents, and check names, dates and role against the hire.
- Chase
The right-to-work document is missing, so we email the new hire, and ask the hiring manager to confirm the start date.
- Decide
Your onboarding rules run in the deterministic policy engine. Anything that doesn't fit goes to HR to decide.
- Act
We create the employee in BambooHR and call the resume URL, so your workflow carries on and provisions the Okta account.
Used in the same case
The connection, in detail.
How it connects.
- 1
Connect n8n
Using webhooks, in both directions. Nothing migrates and nothing is replaced.
- 2
Build your operation
Describe it in Slack, Teams or the Floowed Dashboard. Floowed builds it and asks only what it can’t work out.
- 3
Let it run
Every case runs from request to outcome, the same way each time, with the reasons on record. Anything sensitive waits for a person.
Questions
Does Floowed integrate with n8n?
Yes, over webhooks in both directions, whether your n8n is self-hosted or on n8n Cloud.
How does the n8n integration connect?
An HTTP Request node posts to a Floowed endpoint to start a case. Either a Webhook node catches the decision separately, or a Wait node holds the workflow open and gives us its resume URL to call when the case clears. No node to install either way.
Why not just build the logic in n8n?
For routing, do. But a workflow doesn't read a photographed certificate, chase the person who never sent it, or keep a version history of the rules that decided. Those are the parts we do.
Can I keep sensitive data on my own infrastructure?
Yes, and it's a good reason to use n8n here. Self-host it, keep the documents on your side, and send us only what the case needs. Self-hosted n8n sends anonymous telemetry by default, such as workflow shape and error messages without payload data, and N8N_DIAGNOSTICS_ENABLED=false turns it off.
Do I have to replace my workflows?
No. They keep doing what they do. Floowed runs the case in the middle and hands the outcome back to them.
What does the n8n integration cost?
Nothing extra. Integrations are included, and you pay for the work Floowed does on a case. Start free with $80 of credits, no card and no sales call.
Start with n8n. Add the rest.
Free to try, no card, no sales call. Your first $80 of credits is on us.