Workflows

A task is a one-off. A workflow is a job you do the same way every time, laid out once as a set of steps so you never have to describe it again.

Good candidates: the Monday report. Triaging the support inbox. Turning a finished recording into a transcript, a summary and a set of clips. Anything where you find yourself typing almost the same instruction for the third time.

Choose WORKFLOWS along the bottom of the window.

The workflows panel, empty, inviting you to create one

You start with none. Use the + to make one.

When a workflow is waiting on you, the WORKFLOWS button carries an orange badge with the count, in the same way the approvals button does.

What starts it

Every workflow needs a trigger. There are five:

Trigger When it runs
โšก Manual Only when you say so
๐Ÿ“… Scheduled On a timer, daily or weekly
๐Ÿ”— Workflow When another workflow hands off to it
๐Ÿ“ก External Event When something happens on a connected platform
๐Ÿ“ž Call Completed When a phone call ends

Call Completed needs telephony, which is not switched on in shipped builds. If your version offers it, nothing can fire it. Ignore it.

Start with Manual. Build the workflow, run it by hand a few times, fix what is wrong, and only then give it a trigger that fires without you.

About scheduled workflows

Choose daily or weekly, then a time โ€” and for weekly, a day.

The panel carries a warning you should take literally:

โš  Scheduler only runs while the app is open.

GNexusOS is a desktop application, not a service running somewhere else. A workflow set for 7am will not run if your Mac or PC is asleep and the app is closed. If something genuinely has to happen whether you are there or not, a scheduled workflow is the wrong tool.

Building the steps

A workflow is a diagram. You add nodes and connect them.

There are two kinds of node:

+ ACTION โ€” an agent does something. You give it:

  • Step Name โ€” what this step is called, for example Route Email or Summarise Report.
  • Agent โ€” which agent does it.
  • Instruction โ€” what it should do, in your own words.
  • Output Type โ€” the kind of result, as in the dispatch bar.
  • Target Resource ID (optional) โ€” paste an existing resource to write into, or leave blank to create something new.
  • Next Step โ€” where to go afterwards. This can be another step, or a different workflow entirely.

+ DECISION โ€” an agent decides something, and the workflow branches. You give it a name, an agent and an instruction phrased as a question. Then you add branches, each with a label like Yes, No or Approve, and each pointing at the step or workflow that follows.

AUTO-LAYOUT tidies the diagram when the boxes have wandered.

When a workflow pauses

A running workflow can stop and wait for you. When it does, the pending item offers:

Button What it does
APPROVE Let the step go ahead
SKIP Move past this step without doing it
CANCEL Stop the whole run

At a decision point there is also an override field. Type the label of the branch you want and choose OVERRIDE to send the run that way regardless of what the agent decided. This is the manual steering wheel โ€” useful when you can see the agent is about to take the wrong turn.

Run history

Underneath the pending items is RUN HISTORY: every time this workflow has run and what happened.

Read it after the first few runs of anything new. A workflow that fails in the same place every Monday is telling you something specific, and the history is where you see the pattern.

A sensible way to build one

  1. Do the job by hand with the dispatch bar two or three times first. You learn what the steps actually are.
  2. Build it as a Manual workflow with those steps.
  3. Run it manually and read the run history.
  4. Add a decision node only where you genuinely found yourself choosing.
  5. Give it a real trigger last.

Workflows built from a job you have actually done work. Workflows built from a job you imagine doing usually need rebuilding.

Related