Workflows overview
Workflows (also called Proto Workflows) automate work in your app. A workflow starts with a trigger (something happens) and runs a chain of nodes (steps). Examples:
- When an Order is created, email the account manager.
- When a Leave Request is updated to Submitted, route it to the employee’s manager for approval.
- Every morning at 8 AM, find overdue invoices and post a summary to Slack.
- When a Stripe payment succeeds, create a Payment record and mark the invoice paid.
- When a user clicks a custom action button, send the selected records to an outside API.
The Workflows page
In the app sidebar, click Automation → Workflows.
| Area | What it shows |
|---|---|
| Summary cards | Proto Workflows (total and active), Executions (with the count for the last 24 hours), Success Rate, Failures (with View details), Avg Duration, Queue (with View queue) |
| Filters | All, Active, Inactive, Failing, plus a search box |
| Time range | 24h, 7d, 14d, 30d, or 90d for the summary cards (test runs are excluded) |
| Display | Cards, Table, or Analytics view, sorted by Newest First and other options |
| Connections (key icon) | Opens App Settings → Connections to manage integration credentials |
| + New workflow ▾ | Blank (start from scratch), From Template, or Create folder (group workflows into folders) |
Workflow templates
Click + New workflow ▾ → From Template to start from a ready-made automation, for example:
- Email Support Tickets: turns incoming support emails into ticket records, removes duplicates by thread/message ID, and sends an acknowledgement
- SLA Policy Tracker: tracks SLA compliance on support tickets with response, resolution, and restoration targets for each priority
Filter templates by category (for example Support) or search for one, then click Use Template.
How workflows run
- A workflow runs only when it’s Active. New workflows start as Inactive.
- Every run appears under Runs in the workflow editor. See Workflow settings and runs.
- Workflow runs, code compute, agent executions, and trigger/webhook activations are billed from your credits. See Pricing.