Workato, ready to run.
The Workato integration lets your recipes and Floowed operations work together. A recipe can open a case in Floowed, and a case can call a recipe when it needs something done in a system Workato already reaches.
What it does.
What Floowed reads from Workato
- New cases sent from a Workato recipe
- Records and files a recipe has pulled from connected apps
- Results from a recipe that a case is waiting on
What it writes back
- A webhook call that starts a recipe, with the case data attached
- The outcome and its reasoning, for the recipe to act on
- Status updates as a case clears or waits on a person
If Workato already connects your ERP and HR systems, let recipes do the system updates and let Floowed handle the documents, chasing and rules checks. Pass the case ID into the recipe so every job in Workato ties back to a case in Floowed.
How it connects.
- 1
Connect Workato
Using an API key. 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 Workato?
Yes. Workato and Floowed connect over webhooks and an API key, so recipes can start cases and cases can start recipes.
What can Floowed do in Workato?
It opens cases from recipes, calls recipes at any step of a case, and returns the outcome with its reasoning for the recipe to use.
Is my Workato data secure?
Floowed only gets the access it needs in Workato, never stores a password, and logs every read and write with the reason.
What does the Workato integration cost?
Nothing extra. Integrations are included in every plan, and you only pay for the work your operations do.
Start with Workato. Add the rest.
Free to try, no card, no sales call. Your first $80 of credits is on us.