Make, ready to run.
The Make integration is a division of labor. Make moves the work between your systems, which it does well. Floowed runs the case around it: it reads what arrives, chases what is missing and applies your rules, which a scenario was never built to do.
What it does.
What Floowed reads 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
What it writes back
- 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
Make's records are records of the automation, not of your business, so there is nothing here worth syncing back. A case can wait days for a document, so the pattern is one scenario that starts the case and a custom webhook that catches the decision when it lands.
A supplier onboarding case, from request form to vendor record.
- Gather
A supplier submits your Google Forms request and a Make scenario posts it to Floowed, with links to the files they uploaded to Google Drive. The case opens.
- Interpret
We read the tax form, the bank letter and the insurance certificate, and check each against what the supplier declared on the form.
- Chase
The certificate has expired, so we email the supplier for a current one and follow up until it arrives.
- Decide
Your onboarding rules run in the deterministic policy engine. A supplier outside them goes to procurement to decide.
- Act
We create the vendor in NetSuite and call your custom webhook, so the next scenario tells the requester the supplier is live.
Used in the same case
The connection, in detail.
How it connects.
- 1
Connect Make
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 Make?
Yes, over webhooks in both directions. A scenario can start a case in Floowed, and Floowed hands the outcome back for a scenario to act on.
How does the Make integration connect?
An HTTP module in your scenario posts to a Floowed endpoint to start a case, and Floowed calls your custom webhook when the decision lands. Two scenarios rather than one, so nothing sits open while a case waits for a document. Nothing to install on either side.
Why not just build the logic in Make?
Scenarios route well. No router reads a photographed certificate, chases the document that never arrived, or keeps a version history of the rules that decided. That is the part we do.
Do I have to replace my scenarios?
No. They keep doing what they do. Floowed runs the case in the middle and hands the outcome back to them.
Is data sent through Make secure?
Anything crossing Make is subject to Make's own handling, so we don't route sensitive documents through it. Send us a reference and we fetch the file from the system that holds it.
What does the Make 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. Make bills its own credits separately.
Start with Make. Add the rest.
Free to try, no card, no sales call. Your first $80 of credits is on us.