How flows work

Flow is the earlier way to automate the work that follows a meeting or a file upload. Automations have taken over, so new flows can no longer be created. Your existing flows work as they always have: you can run them, edit them, pause them and delete them.

Build anything new as an automation. You pick a destination, the content and the conditions in a short form, and Klang sends the meeting report automatically after every meeting. Nine destinations are included, plus a webhook to any system.

Find your flows

The Flows tab sits in the left menu as long as you have at least one flow. It lists every flow in the workspace with its status: active, paused, or not automated.

Click a flow to open it. From there you can run it, change its trigger, or open the editor.

What a flow is made of

A flow is a series of steps connected in a visual editor. Each step is a node that does one thing: reads a file, generates a summary, sends a Slack message, or saves to Google Drive. Data moves through the nodes from start to finish.

The editor uses a drag-and-drop canvas. Add nodes from the sidebar, connect them with lines, and configure each one by clicking it.

Running a flow

There are two ways:

• Manually: open the flow, click Run, pick the file you want to process, and review the result
• With a trigger: set the flow to run when new content arrives, for example every time a transcription finishes or a file lands in a specific folder

Manual runs suit one-off tasks. Triggers suit the case where the same processing should apply to every new file.

What happens to Flow

Flows are still supported and run the way they always have. We are not adding features to Flow, and new flows cannot be created. Build what you need going forward as automations.

Next steps

• Using flow triggers to run an existing flow automatically
• Introduction to automations to set up something new