THE DECISION PLATFORM
Make, ready to run
Choose. Adapt. Run.
The Make integration is a division of labour. Make moves the work between your systems, which it does well. Floowed makes the decision in the middle, which is the part a scenario was never built to do.
THE INTEGRATION
What the Make integration does
Make is visual automation between apps. 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 Make
- Whatever a scenario sends in, as the start of a case
- Documents and links carried on the payload
- Fields from any app in your Make account, carried in by the scenario
Some of what we write back to Make
- The decision and its reasoning, back to the scenario
- The outcome, on to whatever the scenario does next
- A callback when a case that was waiting finally clears
Examples, not a list of limits. A decision can read anything the Make API exposes and write back wherever it allows it, so tell us what yours needs to see.
Make's own API reads scenario state and execution logs, but those are records of the automation rather than records of your business, so there is nothing here worth syncing back. The thing to design around is that a scenario runs start to finish and cannot pause to await an answer: its longest sleep is five minutes, and a case can wait days for a document. So this is one scenario to start the case and a second webhook to catch the decision, which is what Make's own documentation recommends for exactly this shape.
THE LIBRARY
Decisions that run on Make
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 Make 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 Make
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 Make integration connects
Choose
Pick the decision from the library. It arrives already built, carrying what earlier runs taught it.
Adapt
Connect Make using Webhooks, in both directions, then set the rules and the gates to yours. You decide how much it decides.
Run
Every case runs the same way, with the reasoning attached and a full audit trail. Anything sensitive waits for a person.
NEARBY
FURTHER READING
QUESTIONS
Make integration FAQ
Does Floowed integrate with Make?
Yes, over webhooks in both directions. A scenario can start a case in Floowed, and Floowed hands the decision back for a scenario to act on.
How does the Make integration connect?
Your scenario posts to a Floowed endpoint to start a case, and Floowed calls your webhook when the decision lands. Two scenarios rather than one, because a Make scenario cannot hold itself open waiting. Nothing to install on either side.
Why not just build the logic in Make?
You can, until the logic is real. Scenarios branch well and judge badly, and no router reads a photographed bank statement, chases the document that never arrived, or keeps a version history of the policy that decided. That is the part we do.
Do I have to replace my scenarios?
No. They keep doing exactly what they do. Floowed sits above them and makes the call none of them was built to make.
Is data sent through Make secure?
Anything crossing Make is subject to Make's own handling, so we would not route sensitive documents through it. Send us a reference and we will fetch the file directly from the system that holds it.
What does the Make integration cost?
Nothing extra from us. Integrations are included, and you pay for the work Floowed does on a case. Make bills your operations separately.
Start with Make. Add the rest.
Free to try, no card, no sales call. We front you $80 of credits to run the first cases.