The flow list
Reading the list of flows, and creating a new one.
Signal flows in the sidebar opens the list of every flow in the system. The order matters: flows are checked against an incoming message from the top down, and the first claim that matches wins.
Reading the list
| Column | What it tells you |
|---|---|
| Flow | The name, and the way in to its workspace |
| Answers messages that | The claim in plain language — the words it starts with, the pattern it matches, or that it is the fallback |
| Status | Draft or Published |
| Last edited | When the configuration last changed |
A claim shown as not set yet means the flow has been created but its first wizard step is unfinished. Such a flow cannot be published.
Creating a flow
Choose New flow. Three things are asked for up front; everything else is decided in the wizard.
Name
What the flow is called, for example Impuruza community signals. A key is generated from the name and shown beneath it.
Description
What this flow is responsible for, in a sentence. This is for the humans maintaining the configuration.
Which messages does it answer?
Pick one of the three claim types. Choosing starting words or a pattern here only records the intent — the actual words or expression are entered in the wizard's first step.
The key is permanent
The key is generated from the name and is fixed once the flow is created. Renaming the flow later changes the display name but not the key, so it is worth getting the name right the first time.
Names must be unique. Creating a flow lands you in its workspace on the first wizard step, with the flow saved as a draft.
Deleting a flow
A flow can be deleted from its row in the list. Deleting a published flow releases the messages it claimed, which will then fall to whichever flow claims them next — check that before deleting, particularly if the flow being removed is the fallback.
Where to next
With a flow created, work through the wizard.