Workflows

Feature on video · Length 0:31

Some work repeats itself every day in the same order. A workflow is the place where that routine is written down once: a trigger as the starting point and then any number of steps that run one after another or branch out.

What a workflow consists of

Every workflow belongs to exactly one space and consists of exactly one trigger plus the nodes behind it. The nodes process the incoming data step by step and can perform actions in other systems at the end – create a draft or file a document, for example.

A workflow is created via the sidebar and “New workflow”: choose the space, give it a name, start empty or import an existing workflow file. It starts as a draft and only goes live when it is published. Creating, editing, publishing and test runs require the “Manage workflows” right in that space.

What starts it

The trigger decides when the routine starts. It can be a schedule, a webhook from one of your own systems, a manual start by click or an event from a connected integration – an incoming email, a mention in a chat or a new ticket.

Typical uses: read incoming requests, classify and answer them, create a preparation document for every meeting, or generate and send a scheduled report.

Approve and read back

A workflow does not have to run straight through. Multi-stage processing with human approval is explicitly one of its uses: at the point where a decision is made, the routine stops and waits for a person.

What has run is listed under “Runs”: past executions including filters, next to it the “Integrations” tab with the connections to external services. What the automation did and when stays traceable.

What is said in the video

The spoken text of the video, section by section.

  1. Some work repeats itself. Every day, in the same order.

  2. Read the request, classify it, forward it, file it. By hand, over and over.

  3. A workflow captures that routine: a trigger and the steps that follow.

  4. The trigger is a schedule, an incoming message or a click. After that the flow runs on its own.

  5. And where a decision belongs, it waits for your approval. Every run stays on the record.

  6. Workflows in skai. More on our website.