Skip to main content
A dynamic workflow is a coworker’s plan for a job too big for one pass: a team of temporary helpers working side by side.
Off for now. Coworkers don’t run dynamic workflows for now, and nothing else in the app runs them either: not the Concierge, and not a workflow or a schedule. Sessions from before keep their run cards, and saved dynamic workflows stay in your coworker’s files, but your coworker can’t run one.

A narrated tour, so turn your sound on. Ivy, a support coworker, groups 200 tickets by theme with a team of helpers, then keeps the run to use again.

What it does

Some jobs aren’t hard, they’re just big. Two hundred support tickets to group by theme. Twenty companies to research before Thursday. A year of meeting notes to boil down. Your coworker starts by writing a plan: the phases the job breaks into. Then it hands the work to temporary helpers. Each one takes a slice, works on it alone, and reports back. Your coworker pulls their reports into one answer, and the helpers are gone when the job is done. These run-only helpers aren’t your coworker’s custom helpers, the named specialists you set up yourself. A run can put those to work too.

Who has it now

Nobody, for now. A run puts a whole team of helpers to work, so it costs far more than an ordinary session, and coworkers are kept from starting one. There’s no switch for it: the Capabilities tab no longer lists Dynamic workflows.
The switch below was on the Capabilities tab before. It isn’t there now.
The Dynamic workflows row switched on, with an orange line underneath saying Code and files must be turned on too

The warning sits on the row itself, so the switch never reads as on while nothing happens.

For a big job now, your coworker works through it in its session, or hands parts to other coworkers in its agent. It can also use the custom helpers you set up for it.

What a run looked like

Each run had its own card in the conversation, and sessions from before keep them. Here’s the one from Ivy, a support coworker, partway through grouping 200 tickets by theme.
The ticket-themes run card: Read finished, Check rows showing their latest steps, a stop icon on a working row, a note reading 9 themes in 8 of 8 batches, and a line confirming Slack was approved for this run

Ivy's ticket-themes run partway through. All eight Read helpers are done, and the Check helpers are working through the themes.

1

The plan comes first

Before any helper starts, the card lists the phases the job breaks into, each marked pending. Ivy’s are Read, Check and Report. If that isn’t what you meant, stop the session and say what you want instead.
2

Helpers fill in live

A row appears as each helper starts, showing its latest three steps. A link like +2 earlier shows the rest. Finished rows get a green tick and fold down to a step count. Your coworker can add notes as it goes, like 9 themes in 8 of 8 batches.
3

Stop one that's off track

Every working row has a stop icon: “Stop this agent — the rest of the run keeps going”. It works until the run first pauses. Click it and that helper stops, with no confirmation, while the others carry on. Its row shows a dashed circle, or a red mark if it was stopped mid-step. In Ivy’s run, stopping Check: App crash means that theme isn’t written up in this stretch. A stopped helper’s work isn’t kept, so when Ivy’s run continues after its pause, App crash is checked again and then written up.
4

One answer at the end

When the last helper finishes, your coworker turns their reports into the answer you asked for. The card folds down to a count, like 27 agents, and each row shows what that helper used.
A helper’s row also has a transcript link. It opens that helper’s full working in the session’s files, so you can check exactly what it did.

Letting a run use your apps

A run’s helpers couldn’t touch your connected apps unless the plan asked for them. The one exception was a custom helper with no tool list, which could still do what your permission rules already allowed without asking. Ivy’s plan names Slack, because its last step posts the report to #support-leads. When a plan named an app, you were asked once, before anything ran. The plan appeared on the card once you approved.
An approval card headed Let “ticket-themes” use Slack, with only Decline and Approve buttons and no Always allow

One question for the whole run. There's no Always allow, because every run asks for itself.

  • Approve let any of the run’s helpers, up to 30, use Slack without asking again. The permission ended with the run, and the card keeps a line saying Using Slack — you approved this for this run.
  • There was no Always allow. A standing rule would have approved the apps of every future run, so each run asked on its own.
  • A “never” rule still won. Approving a run couldn’t override a permission rule that says Never. Anything else that needed your yes was refused, and the helper said so in its report.
  • Decline, and nothing had run, so nothing was lost. Your coworker could rework the plan without the app.

Long runs

A big run didn’t have to finish in one go. After about ten minutes of work it paused, then picked up again on its own straight away.
The ticket-themes card reading 14 done · continuing with its paused notice, followed by a row showing the run started again on its own

Ivy's run pauses at 14 done, then starts its next stretch on its own. Finished helpers aren't run again.

While it was paused, the header read 14 done · continuing and the card said:
Too big for one turn — continuing on the next one. Finished agents are replayed, not re-run.
In plain terms: helpers already working finished first, and finished helpers weren’t run or paid for again. The next stretch appeared in the conversation as Started on its own.

Saved dynamic workflows

A completed run’s card used to offer Make repeatable, to keep a run that turned out well. Its tooltip read “Saves this run as a dynamic workflow, then adds it to Workflows with a trigger that runs it.” A coworker’s run cards no longer offer it, and the app refuses it if it is asked anyway: the workflow it builds hands the run to a coworker, so it could never run. A card made repeatable before still links to its workflow. What it made before is kept, but your coworker can’t run a saved dynamic workflow for now. The slash menu in a coworker’s session no longer lists them, and a workflow or a schedule that asks a coworker to run one doesn’t get that work done.
The finished ticket-themes card folded down to 27 agents, with the Make repeatable button and its tooltip above it

Make repeatable appears only on a run that completed. Ivy's ticket-themes run is ready to keep.

Clicking it made two things, and the message said so: “Saved as the ticket-themes dynamic workflow and added to Workflows, with a trigger that runs it.”
  • A saved dynamic workflow. It’s kept in your coworker’s own files, in the .workflows/ folder of its Files tab, where you can read it.
  • A separate workflow, in the session’s agent. It isn’t the dynamic workflow itself. It has a Start trigger, then one step that asks Ivy to run ticket-themes. For now, Ivy can’t do what that step asks.
A workflow canvas with a Start node connected to a step titled ticket-themes, badged with the coworker Ivy

The workflow that Make repeatable builds: a Start trigger, then one step that hands the ticket-themes job to Ivy.

Make repeatable never overwrote a different dynamic workflow with the same name: it saved the new one beside it, as ticket-themes-2. See Dynamic workflow scripts.

Under the hood

The plan was a short script, built from a handful of building blocks: agent, parallel, pipeline, phase, log, budget and args. To read a saved one part by part, see Dynamic workflow scripts.

Good to know

Six at a time, 30 in all, within a spending limit. A run used up to six helpers at once, and up to 30 in all, within a spending limit your coworker set for it.
Results live in the session’s files. Each helper’s transcript was saved there, and so was any result too long to hand back in full. Like all session files, they’re discarded with the session’s cloud computer when it ends. Download anything you want to keep, or ask your coworker to save it to Workspace files.

Common questions

Not for now. Coworkers don’t run them, and nothing else in the app does either. For a big job, your coworker works through it in its session, hands parts to other coworkers in its agent, or uses its custom helpers.
They’re kept in your coworker’s files, in .workflows/, and the workflows that Make repeatable built stay in Workflows. Your coworker can’t run a saved one for now, so a workflow step that asks it to doesn’t get that work done.
Because every helper on the team was paid for. Each row on a run’s card shows what that helper used, though after a pause, rows finished in an earlier stretch show none.
Only with your yes. When a plan named an app, you approved it once, before anything ran, and the permission ended with the run. See Letting a run use your apps.

Next steps

Dynamic workflow scripts

The building blocks behind every plan.

Custom helpers

Named specialists your coworker can call on in any session.

Working with code and files

How your coworker works through a big file on its own.

Working with coworkers

Hand work to a real coworker instead.