DocsOpen Henkan Chat
Flows

Automate with flows

Flows run investigations across your connectors on a schedule, when something happens in a tool, or on demand, and deliver a report.

Up to date with v1.5.4Updated 30 October 20263 min read

Flows run the investigations you would otherwise repeat by hand, and deliver the report by email, Slack or Notion. They run on a schedule, when something happens in one of your tools, or when you start them.

A flow fetches data from your tools, checks a condition, lets Henkan analyse what it found, then writes the report.

Flows are in the Pro, Max and POC plans. On the Free plan the Flows page shows Flows are available on Pro and Max — talk to Henkan; Flows you already made are kept and run again after a plan change. See Requests and plans.

The Flows page, with the five templates.
1
New flow. Starts from a blank canvas.
2
Templates. Create a ready-made flow bound to your connections.

Create a flow#

  1. Open Flows In the sidebar, select Flows.
  2. Pick a starting point Select Use template on a template card, or New flow for an empty canvas. The flow opens in the editor, switched off.
  3. Fill in the parameters Templates use parameters such as client or ga4_property. Open ⋯ › Parameters in the editor to fill them in. See Build a flow.
  4. Test it Select Test run and follow the run on the canvas.
  5. Switch it on Turn on the On switch. A flow can only be switched on when it has nothing left to fix.

Templates are bound automatically to your first connection of each tool. If you use Wingify instead of Kameleoon, test blocks switch to their Wingify equivalent. See Flow templates.

Your flows#

Your flows, with sample data.
1
Client and trigger. The flow's client parameter and when it runs.
2
Last result. How the last run went, and when it ran.
3
On/off switch. Turns the flow on or off.
4
Actions menu. Edit, run now, duplicate, run history or delete.

Each row shows the flow's name, its client parameter if it has one, its trigger (for example Every Monday at 08:00, Daily at 09:00, When an event happens or Manual), the next scheduled run, the last result and the on/off switch.

Last resultMeaning
SuccessEvery block finished.
WarningThe run finished, but something needs your attention, for example an email that could not be sent or a merge that continued with partial results.
ErrorThe run stopped. Open the run history to see which block failed and why.
RunningA run is in progress.
Never runThe flow has not run yet.
Menu actionWhat it does
EditOpens the flow in the editor.
Run nowStarts a run immediately and opens it on the canvas.
Duplicate for another clientCopies the flow with a new name and new parameter values, for example another site or GA4 property.
Run historyOpens the editor with the list of past runs.
DeleteDeletes the flow and its run history after confirmation.

Flows shared with you#

Flows colleagues shared with you appear under Shared with me below your flows, with who shared them and your access: Can view, Can run or Can edit. Runs you start use your own connectors, and their report is saved in your own conversations.

To share one of your flows, open it and select Share in the editor toolbar. See Share with colleagues.

Other ways to start a flow#

FromHow
The chatType /flow and the flow's name. See Ask a question.
SlackIn a direct message to Henkan, write run flow and the flow's name. See Henkan in Slack.
Claude, ChatGPT or CursorAsk the assistant to run it. It uses the henkan_run_flow tool. See Use Henkan in other AI tools.