ExecutionRoom 02 of 13
Automations you can see.
Drag-and-drop a workflow, or just describe it and let Sophon draft it. Triggers, logic, approvals, sub-workflows: 20 node types on an infinite canvas, and since 2.2 every run is recorded, watched live, and debuggable step by step.
Workflow: a Cron schedule trigger starts two branches that run side by side, Calendar and Top emails. Both feed a Summarize step, which sends the briefing to WhatsApp.
00/05 Idle. Waiting for the trigger.
Recreation of the workflow builder, with sample data.
AWatch a morning briefing run
One workflow, start to finish.
A morning briefing: a trigger, two sources read in parallel, a summary, a message.
Workflow: a Cron schedule trigger starts two branches that run side by side, Calendar and Top emails. Both feed a Summarize step, which sends the briefing to WhatsApp. Running: trigger.
Cron schedule · A standard cron expression, for example 0 9 * * MON, while the workflow is enabled.
Step 1 of 5: Pick what starts it
01 / 05 · Pick what starts it
One trigger per workflow decides when it runs. Five can fire: cron schedule, webhook, channel message, email received, and manual. File change, calendar event and agent request never fired, so since 2.2 a save that adds one is refused. Swap the trigger on the stage. The rest of the workflow stays as it is.
BTriggers
Five ways to start a run.
One trigger per workflow. It decides when the run starts; the nodes after it decide what happens. Since 2.2 the event triggers fire, and every run executes as the workflow's owner.
- Cron schedule
- A standard cron expression, for example 0 9 * * MON, while the workflow is enabled.
- Webhook
- An authenticated POST to the workflow's webhook route, or a signed request to an inbound webhook registration (Bearer, HMAC-SHA256 or a custom header).
- Channel message
- An inbound message on a channel the workflow's owner connected, matching your filters. WebChat never fires it.
- Email received
- A new mail in an IMAP inbox the workflow's owner connected, matching sender, subject and pattern filters.
- Manual
- You press Run in the Dashboard or run sophon workflows execute, or an agent calls workflow.trigger.
CRuns and debugging
Every run, on the record.
New in 2.2: runs are durable records you can watch, cancel and pick apart, and a failing step can be tested on its own before you run the whole workflow again.
- Durable runs, watched live
- Every run and every step attempt is stored, with secrets redacted, and streamed live to a run viewer drawn on the canvas. Start a long run without waiting for it, cancel one still going, and open any step's inputs, output, timing and error. Runs from v2.1 history are imported once.
- Test one step
- Run a single step with mock outputs, a recent run's data, or the sample input you pinned for the workflow, and see what each reference resolved to. A step that can change something outside Sophon asks before the test runs it.
- Re-run from here
- Start a finished run again from the step you choose. The outputs of the steps before it are carried over, and a re-run asks before it repeats a step with an outside effect.
- Cost per step
- LLM prompt steps record the model they ran on, their tokens and their cost. API call response bodies are capped, at 1 MB by default.
- Kept for 30 days by default
- Runs are pruned after 30 days, keeping at least the newest 20 and at most 500 per workflow. An operator can change the retention and the per-owner and per-tenant run caps in the Gateway's settings.
DMechanism
Twenty node types after the trigger.
Wire them into a DAG. Steps run one at a time unless you opt in with a Parallel step or a concurrency of up to 8. Where branches meet, the next step runs once. Anywhere a node takes a value, a mustache expression can read an earlier step's output, a workflow variable, or the trigger payload.
- Actions
- Run skill, LLM prompt (optionally pinned to a provider and model), Send message to a channel the workflow's owner can use, Execute code (Python or C# in the sandbox), API call, and Create or update file, which writes only inside the workflow's own files folder.
- Logic
- If / else, Switch, Wait for a duration, Loop (for each item, or while a condition holds) that repeats its body branch, Parallel, which opts the run into running branches side by side, Merge, which collects the branches that ran, and an Error handler that routes failures to a recovery branch.
- Data
- Transform, Filter, Aggregate (count, sum, min, max, join), and Set variable, which binds $vars.<name> for the rest of the run.
- Approval
- An Approval gate pauses and routes on the outcome, such as approved, rejected or timed out. An Info request asks a question and its answer becomes the step's output. Both go to the workflow's owner, with a link to the run.
- Sub-workflow
- Runs another workflow you own, inline, and its result becomes the node's output, so building blocks are reusable.
Expressions
{{ $node.fetch_orders.output.items }}
{{ $vars.threshold }}
{{ $trigger.data.userId }}
{{ default($vars.note, 'none') }} # optional value
{{ $vars.count > 10 }} # comparisons in If nodesESpecifics
Governed by default.
- A canvas, not a config file
- Drag nodes onto an infinite canvas, wire them together, and watch data flow. Pan, zoom, and follow a run step by step. Underneath, a workflow is JSON in ~/.sophon/workflows/.
- Buildable without the agent
- Since 2.2 every step shows a readable id, and typing {{ opens a picker of the references you can use, with Insert and pick-on-canvas. Renaming a step rewrites the references to it. Edge conditions and switch cases have their own editors, the trigger sits on the canvas, the Gateway's issues show before Save, and undo and unsaved-change prompts keep your edits.
- Described, then drafted
- Describe what you want in plain English and the agent generates the workflow JSON, then shows an approval dialog with a plain-language summary, the node count, estimated risk, and required credentials. Approve, Edit in Builder with the draft preloaded, or Cancel. Tweak it visually, or let it keep iterating.
- References that fail loudly
- In a workflow created since 2.2, a reference that doesn't resolve fails the step instead of sending the literal {{ … }} text. Wrap optional values in default(…). References to later, failed or skipped steps are flagged when you save.
- Every save is a version
- Older versions stay queryable. View a diff between two versions, roll back in one click, or fork an old version into a new workflow.
- Credentials by reference
- Nodes reference connections by ID instead of embedding secrets, so changing a credential doesn't require re-approving the workflow.
- Owned, in a team
- On Pro and Enterprise a workflow belongs to its owner. Only the owner or an Admin of the tenant edits or runs it, every run executes as the owner, with the owner's credentials, and ownership moves only by transfer. Viewers can't create, edit or run workflows.
- Templates
- The Dashboard ships a template library: Morning briefing, Email summary, Data pipeline, Approval flow, and, new in 2.2, Web Digest, which fetches a page each morning, summarizes it and posts the digest. Every template's steps carry readable ids.
From the CLI
sophon workflows validate digest.json # issues, nothing saved
sophon workflows execute digest # follow the run, exit by its outcome
sophon workflows execute digest --async # print the run id and return
sophon workflows runs digest --status failed
sophon workflows run wfr_… --details
sophon workflows cancel-run wfr_…Limits
Where workflows stop.
One trigger per workflow.
TriggersFile change, Calendar event, Agent request triggers cannot fire. A save that adds one is refused, and a stored workflow that has one never runs on its own.
TriggersInbound webhook registrations have no replay protection: a replayed signed request starts another run. Keep the endpoint behind TLS and rate-limit it at your reverse proxy.
WebhooksDAGs must be acyclic. The builder validates on save and refuses cycles.
Limits and gotchasLoop iterations run one at a time, and loops cannot nest.
Limits and gotchasExpressions are not JavaScript. Complex logic belongs in an Execute code node.
ExpressionsSub-workflows nest at most 5 deep.
Limits and gotchasA run that is in flight when the Gateway restarts is marked Interrupted and is not resumed. Re-run it by hand.
Limits and gotchasThe mobile app has no run viewer or debug tools yet. Its Run gives up after 15 seconds, so a longer run, or one waiting on an approval, shows as failed there while it carries on.
MobileThe Morning briefing template's calendar step calls calendar.today, which no skill provides yet.
TemplatesThe agent cannot silently create a running automation. AI-authored workflows always go through the approval gate, even if you trust the agent.
AI-authored workflowsShared workflows need Pro or Enterprise. Sharing never lends credentials: every run uses the owner's.
Shared workflows