THE DECISION PLATFORM

n8n, ready to run

Choose. Adapt. Run.

The n8n integration keeps the routing with n8n and the judgement with Floowed. Your workflow moves the work; we read what arrived, chase what is missing, and decide what happens next.

Connects by
Webhooks, in both directions
Category
Automation
Reads and writes
3 in, 3 out

THE INTEGRATION

What the n8n integration does

n8n is workflow automation, self-hosted or cloud. Floowed connects to it, reads what a decision needs, and puts the outcome back where your team already works. Nothing migrates and nothing is replaced.

Some of what we read 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

Some of what we write back to n8n

  • 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

Examples, not a list of limits. A decision can read anything the n8n API exposes and write back wherever it allows it, so tell us what yours needs to see.

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.

THE LIBRARY

Decisions that run on n8n

These are library flows, already built. Choose one, adapt it to your systems and your rules, and Floowed runs every case: reading and interpreting what arrives, chasing what is missing, and deciding what happens next.

  • Supplier onboardingProcurement
  • Employee offboardingPeople
  • Claims intakeInsurance
  • Customer onboardingBanking
  • Vendor risk reviewRisk
  • Credit limit increasesFinance
  • Tenant screeningReal estate
  • Contractor clearanceConstruction
  • Refunds and goodwillRetail
  • Loan approvalLending
  • Crew sign-onShipping
  • Property closing checksLegal

These are where n8n comes up most. A decision is described rather than picked from a menu, so if yours is not here, it is a conversation rather than a no.

AND FURTHER

It goes further than n8n

The same decisions reach the systems most platforms cannot. Core banking, credit bureaus, KYC providers and insurance cores have no app to install: they start with an agreement and credentials issued to you. Some are a modern OAuth API once you have them, others are SFTP, SOAP or mTLS. We connect whichever it turns out to be.

  • Notion
  • Sage
  • Experian
  • Equifax
  • Guidewire
  • SAP
  • Temenos
  • Salesforce
  • Mambu
  • Duck Creek
  • NetSuite
  • Plaid

Not listed is not the same as not possible. We connect over REST, OAuth, API keys, webhooks, SFTP, SOAP, mTLS and direct database reads, so if a system has an interface of any kind we can reach it. Ask us about the one you are worried about.

SETUP

How the n8n integration connects

  1. Choose

    Pick the decision from the library. It arrives already built, carrying what earlier runs taught it.

  2. Adapt

    Connect n8n using Webhooks, in both directions, then set the rules and the gates to yours. You decide how much it decides.

  3. Run

    Every case runs the same way, with the reasoning attached and a full audit trail. Anything sensitive waits for a person.

NEARBY

More integrations in automation

Browse every integration

QUESTIONS

n8n integration FAQ

Does Floowed integrate with n8n?

Yes, over webhooks in both directions, whether your n8n is self-hosted or on their 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 same workflow open and hands us a 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 nothing in a workflow reads a photographed bank statement, chases the supplier who never sent the certificate, or keeps a version history of the policy that decided. Those are the parts that make a decision defensible.

Can I keep sensitive data on my own infrastructure?

That is the best reason to use n8n here. Self-host it, keep the documents on your side, and send us only what the decision needs. We would rather see less. Worth knowing that n8n self-hosted still reports workflow shape and error messages back to n8n by default, though never your execution data or credentials, and a single environment variable turns even that off.

Do I have to replace my workflows?

No. They keep doing what they do. Floowed makes the call none of them was built to make.

What does the n8n integration cost?

Nothing extra. Integrations are included, and you pay for the work Floowed does on a case.

Start with n8n. Add the rest.

Free to try, no card, no sales call. We front you $80 of credits to run the first cases.