Workflows
A workflow passes one job between several bots and you, in an order you draw.
What a workflow is
One bot looks something up, another drafts, you approve, and a third sends it. A workflow draws that teamwork on a canvas, and Opisense, not the bots, decides who goes next. Each run shows where it is: which bots are done, which one is working, and what waits for you.
A workflow is a kind of routine. It uses the same triggers and appears in its first bot’s Routines list, where opening it opens the workflow. The first bot after the trigger is the lead bot. Each bot uses its own model, instructions, memory and connected apps.
Draw one, or describe it
Open Explore (the grid button at the bottom of the sidebar) and choose Workflows.
- Describe the job in the box, for example “When a lead comes in, Scout looks up the company, Writer drafts a reply, I approve it, and Outreach sends it.” Opisense drafts a workflow from your bots and opens it. It only uses bots you already have.
- Or choose New workflow and draw it yourself.
The editor has Edit and Runs at the top, an Active switch and Test run. Add a trigger, then choose Save.
Bots, You stops, paths and finishes
The toolbar at the bottom adds blocks:
- Bot: one of your bots. Select it to fill in the side panel:
- Its part: what this bot does in the workflow. Improve rewrites it more clearly.
- Hands on: what it passes to the next block.
- Tools: the apps and skills it should use.
- Steps: choose Open to lay out the bot’s own steps inside it, the same way as a routine canvas. Finish early inside a bot becomes one of its paths on the outer drawing.
- You: a stop where the workflow waits for you. Write the question, such as “Send this reply?”. A You stop can have 1 to 4 paths, and the first path is the main button.
- Branch: adds another labelled path out of the selected bot or You stop. When a block has more than one path, every path needs a label, and the bot (or you) picks one each run.
- Finish: where a path ends. An early finish, such as “Held”, ends the run before the last bot.
A path can lead back to an earlier bot, for example “Needs changes” back to Writer.
A bot can appear more than once. Workflows run one block at a time; two bots never run in parallel.
Asking another bot
Ask a bot adds a bot that sits beside the drawing only to answer questions. In the asking bot’s panel, under Asks, say what it asks about and what comes back. A bot can ask up to 3 bots.
During a run the bot asks, waits for the answers, then carries on with them. If an asked bot can’t answer, the asking bot hears why and continues. An asked bot can’t ask another bot.
Inside a workflow, bots reach other bots only along the paths and asks you drew.
Triggers
Workflows use the same triggers as routines: a schedule, a change, a webhook, a Git event, a message (for example in Slack) or an app event. Test run starts one now.
- Webhook, Git event, message, app event and change triggers need a lead bot you made, not a teammate’s.
- App event triggers are set up on web or desktop. iPhone shows them but can’t add one.
- An outside event always starts its own run, even while an earlier run waits for you.
- A scheduled run is skipped while the previous scheduled run is still open.
- Making a different bot the lead moves its webhook and message triggers to the new lead. The editor asks first.
Runs and approvals
Runs draws the latest run on the canvas: the path it took is dark and finished bots have a check. The side panel lists each step with a one-line result and the asks it made. Earlier lists past runs; choose one to redraw it.
Each step also shows in your chat with that bot, so you can follow along. A message you send to that bot while its step runs waits until the step ends.
At a You stop, the run waits for you. The question shows in the run panel, as an approval card in the chat of the bot that handed on, in Needs you, and as a notification. The card shows what is being handed on and, under Started by, what started the workflow. Choose a path, or Edit the text first; the next bot gets your edited version. A path back to an earlier bot lets you add a note.
Steps follow the approval rules of whatever started the workflow. A run started by a webhook, a Git event or a message asks before every action, since outside text could steer it. A scheduled, change or Test run follows routine rules. When a bot step needs approval, that bot shows Waiting for you and the card appears in the run panel and the chat.
Approving at a You stop with the first path vouches for what you approved: the next bot acts on it without asking again. This holds only for that next bot. It doesn’t apply when the card had to shorten the text, or when the next block isn’t a bot. A bot that step asks is trusted the same way.
When a step fails, the run stops there. Retry from here runs that step again with the same input. Cancel run stops a run that is still going. Both are under the … menu in Runs.
Limits
- 60 steps per run, counting asks and You stops. A run that reaches it stops with “Stopped after 60 steps”.
- 3 asks per bot step, one level deep.
- A You stop waits 7 days, then the run ends as Expired.
- A bot with several paths must choose one. A bot that ends without choosing stops the run with “didn’t choose a path”.
- A step whose bot was archived or removed stops the run with its name, such as “Writer is archived”.
On iPhone
Open the home shortcuts menu (the grid button) and choose Workflows. A workflow shows its Latest run as a list of steps and its Earlier runs. At a waiting You stop you can read what is handed on, Edit it, add a note on a path back to an earlier bot, and choose a path. The … menu offers Cancel run and Retry from here. The approval also arrives as the usual card in chat and as a notification.
The iPhone app can’t create a workflow or change its drawing; use the web or desktop app for that.