Why it is still manual

Your process doesn’t run on Tuesday. It runs when Anna is free.

Work done by hand runs at the speed of the person holding it — and it costs most when it is busiest: the week the requests double is the week that person has least room.

Handing it to an agent with tools gets it done, but not the same way twice. Tools tell an agent what it can do, never what it must do — so the steps that have to be identical every time come straight back to the person.

Without it delivered late

Mon Tue Wed Thu Fri Anna in out of office in The job ready waiting sent, late due Wed

With Flow-Plate every Tuesday

Mon Tue Wed Thu Fri Anna in out of office in The job runs 08:00 delivered due Wed

Same work. The only difference is what it waits for.

The mechanism

What you place is what runs.

A workflow is a map of steps. You place them, the software follows them, and nothing improvises.

A request comes in. Five steps later it is in the ERP.

The request itself is the trigger (a webhook). A step checks it against the customer list, the finance lead approves, and a last step posts it. Nothing leaves the building before that yes.

One slot is left empty on purpose. Choose what goes in it — nothing else about the workflow changes.

A person checks it Look it up first Ask an agent Write it yourself Stop if it doesn’t match Leave it out

Nothing past this step runs until a named person says yes.

The step reads what the company already knows and adds it to the request.

An agent handles this one part, sub-configured for this one chore.

Real Python, for when nothing in the catalogue fits.

The run ends here rather than leaving the job half done.

A workflow is allowed to be short. The slot can simply stay empty.

Workflows / month-end-check Editing

the request itself starts itthis one is yours

Request in webhook

Check the customer list

A person checks it human approval Look it up knowledge store Ask an agent sub-flow Your own step python Stop the run flow controlleft empty

Approval finance lead

Post to the ERP

every step opens every change is snapshotted

It runs without anyone asking.

A trigger is the when. On a clock, on a signal from another system, or when another workflow fails — which is how you hear about a break at eight in the morning instead of at the end of the quarter.

Manual Someone presses run — how you try it before you trust it. On a schedule Every Monday at eight, every five minutes, any cron rule you already use. On a webhook The moment another system calls: a task created, a deal moved stage. On an error A workflow that runs when a workflow fails.

Nobody has to be there, and nobody has to know this canvas exists.

Workflows / any workflow at all Armed

You press run manual Every Monday 08:00 schedule A deal moved stage webhook A workflow failed error

Fetch what it needs a connected system

Work out the answer agent step

Deliver it where you said

Armed nobody is watching this

Or anyone asks for it in chat.

Chat is where most people meet the work. One person draws the workflow; everyone it is shared with finds their chat can now do the thing, without ever learning it exists. An agent can call it there too, as a tool.

Nobody opened the builder

Chat / #finance Shared

run the month-end check for me

Using · month-end check Running

done — posted to the channel

Ask anything FTG 4

built by Anna in Sales, once

And an agent follows the same flow. That is the part nobody expects.

The canvas your automations run on is the canvas your agents are built on. Promote an agent onto it and you can see the path it follows — the same steps, in the same order, every time. Demote it and it goes back.

An agent with tools improvises. An agent with a flow repeats.

Agents / order-desk Promote

the path it tookanything not on this flow · never runs

Read the request

Look up the terms

Write the answer

three steps every run takes the same route

1,000+ systems, and yours stay where they are.

Search for the one you need and drop it in as a step. Your ERP stays your ERP, your ticketing system stays your ticketing system, and nobody has to learn a new place to work. Each connection works twice: as a step in a workflow, and as a tool an agent can call when someone just asks.

all 1,062 on the map

Flow-Plate

AC Accounto
AI Aitronos
AC Alturos ContentHub
AS Amazon S3
AC Apple Calendar
AI Apple iCloud Drive
AF Azure Files
BO Box
CL ClickUp
CO Contwise
DR Dropbox
EI Email IMAP
FC Feratel CPSnet
FM File Manager
FI Firecrawl
FR Freshdesk
GE Geosphere
GI GitHub
GM Gmail
GC Google Cloud Storage
GD Google Drive
GM Google Maps
GW Google Workspace
M3 Microsoft 365
ON OneDrive
PI pixx.io
PL Plaud
SL Slack
MT Microsoft Teams
NO Notion
CO Confluence
JI Jira
LI Linear
AS Asana
TR Trello
SA Salesforce
HU HubSpot
PI Pipedrive
ZE Zendesk
IN Intercom
ST Stripe
SH Shopify
XE Xero
QU QuickBooks
AI Airtable
FI Figma
ZO Zoom
GM Google Meet
MI Miro
CA Canva
DO DocuSign
TY Typeform
MA Mailchimp
KL Klaviyo
OP OpenAI
GA Google Ads
MA Meta Ads
DI Discord
BI Bitbucket
GI GitLab
CO Coda
CA Calendly
TO Todoist
BA Basecamp
GA Google Analytics
SN Snowflake
EL Elasticsearch
GB Google BigQuery
SE ServiceNow
BA BambooHR
GR Greenhouse
LE Lever
EV Eventbrite
ST Strava
ME Metabase
AP Apify
AC ActiveCampaign
BR Brevo
HS Help Scout
FR Freshservice
GC Google Classroom
1P 1password
21 21risk
2C 2chat
AB Ably
AB Abstract
AB AbuseIPDB
AB Abyssale
AC Accredible certificates
AC Acculynx
AC ActiveTrail
AD Addressfinder
AD Addresszen
AD Adrapid
AD Adyntel
AE Aeroleads
AF Affinda
AF Affinity
AG AgencyZoom
AM Agent Mail
AG Agentql
AG Agenty
AG Agiled
AC Agility CMS
AH Ahrefs
AM AI/ML API
AI Aivoov
AL Alchemy
AL Algodocs
AL Algolia

Drag to pan

1,062 connected systems · every connection works twice — as a step in a workflow, and as a tool an agent can call

See it run

You can watch the Flows running.

A run is not a log you reconstruct afterwards. Open it and the steps are there in order, each one showing where it got to — done, waiting on somebody, or not started.

Every step opens, and every change to the Flow is snapshotted before it takes effect, so the version that ran is still there to look at.

Runs / month-end-check Waiting

Request in webhook done
Check the customer list your CRM done
Route by region branch done
Approval finance lead held
Post to the ERP your ERP not started

Approve it, revert it, or stop it.

A gate is a step like any other — you place it where the run should wait. Pick one and watch it drop into the Flow.

Human approval Stop on an error Approve a tool

Two of these you place like any other step, and one you set once. None of them needs anybody to write code.

Runs / month-end-check Waiting

Done Check the customer list

Done Route by region

Approval finance lead Stop the run if it doesn’t match Ask before using a flagged tool

Post to the ERP

Nothing past the gate has run, and nothing will until a named person says yes.The run ended here rather than leaving the job half done.The agent has to ask before it uses a tool you flagged.

Who owns it

Nobody here writes code for this.

The person who owns the process is the person who builds it.

Placing a step is choosing it from a list. Not writing one. The catalogue is the palette.
Changing one later is opening the workflow and moving it. The same drawing, edited — not a new version to deploy.
Every change is snapshotted before it takes effect. So a bad edit is one revert away, and the version that ran is still there.

Start here

Start with the one thing you keep explaining.

Not the hardest process. The one you have explained to three different people this year — that one is already written down in your head.

Schedule a demo — 30 minutes on one process of yours

You bring the process; we run it on the call. Nothing to install to watch it, and your data is exportable if you go on to build it.

Flow-Plate is switched on per organisation, in settings.

Pricing Self-hosting Security and data residency