/01
Manual
Kicked off on demand from chat or the dashboard.
Workflow engine
Delegation that becomes durable operations.
A workflow is a durable process graph: repeatable, inspectable, and governable. It can start from a chat message, a schedule, a webhook, a dashboard command, or a connected app event.
Workflow Studio
Design the whole process on one canvas.
A full-screen studio for process design: drag nodes, connect edges, branch on conditions, and publish versions. Test-run it with sample input and watch the run light up the canvas.
A weekly revenue recap: a schedule fires, an agent gathers metrics, a condition checks the variance, a human approves, and the summary lands in Slack.
Triggers
Work can start anywhere.
Five trigger types cover chat, cron, webhooks, and your connected tools. The same graph runs no matter where it starts.
/02
Webhook
Started by an event from any system that can call a URL.
/03
Schedule
Runs on a cron-style schedule: daily, weekly, or whatever cadence the work needs.
/04
Channel message
Triggered by a mention or reply in Slack or Teams.
/05
App event
Fires when a connected tool changes: a new ticket, a deal stage, a deploy.
First-class AI builder
Describe it. SuperEmber builds the workflow.
You don't have to draw every node by hand. Describe the outcome and SuperEmber assembles the workflow (triggers, steps, approvals, connectors) on the same structured package the canvas edits. AI isn't bolted on; it's a native editor.
- Represented as structured data, not a black-box script
- Explainable in natural language, step by step
- Built or edited through structured patches AI proposes
- Validated before publishing, so bad edits get caught early
- Diffable before changes are accepted
- Replayable or testable with sample input
Run history & approvals
Every run is a trust layer, not a black box.
The run inspector shows what happened, why a run paused, and where a human stepped in.
What the run inspector shows
- Trigger and input
- Step status
- Agent tasks
- Fleet delegation and joins
- Connector actions
- Approvals and decisions
- Artifacts and outbound messages
- Errors, retries, and replay
Every step can reach your tools.
Agents, fleets, and workflow actions all run through the same connectors and MCP servers.