Recurring Work, Handled the Same Way Every Time.

Draw the process once on a canvas: what starts it, what decides the branch, what happens next. Workflow Automation runs it when the event fires, records every step, and tells you when a run fails. No code required.

Start Free Trial

Trigger Types

Action Types

Starting Templates

How It Works

Connect a trigger to conditions and actions on the canvas, test it, then activate.

Five Ways to Start a Run

A workflow starts on a platform event (a record created, updated, or changed status), on a schedule you set, on an inbound webhook with an org-scoped token, on a condition, or by hand from the dashboard.

Nine Actions to Choose From

Send a notification or an email, call an outbound HTTP endpoint, wait a set delay, dispatch an AgentHQ agent, update a record, branch on a condition, set a variable, or write a message to the run trace.

Branching and Variables

Condition nodes route the run down a true or false path. Each action stores its output, so a later step can reference the trigger payload or an earlier result with dot notation.

Dry Run Before You Activate

A dry run walks the whole graph and returns the full node trace without writing to the database, sending anything, dispatching an agent, or costing credits. Check the logic first, then turn the workflow on.

A Trace for Every Run

Run history records status, duration, the trigger payload, the variables in scope, and a step-by-step node trace. A failed run sends an in-app and email notification; a run skipped by your concurrency setting is recorded with the reason.

Seven Templates to Start From

Deploy a working workflow and edit it: credential renewal reminders, grant deadline prep, new employee onboarding, monitoring alert response, agent failure escalation, credential expiry compliance, and invoice sync notifications.

Guardrails Included

Automation that touches records and outside systems needs limits around it.

Outbound Requests Are Filtered

The HTTP action blocks requests to private network addresses, so a workflow cannot be pointed at internal infrastructure.

Overlapping Runs Are Your Call

Each workflow sets what happens when a run is already in flight, and the skipped run is logged with its reason rather than dropped silently.

Costs Are Visible

Each run records the credits it consumed on the run record, so automation spend shows up next to the rest of your usage.

Put a Process on the Canvas

Workflow Automation is included on the Enterprise plan. Start with one of the seven templates, dry run it, and activate when the trace looks right.

Start Your Free Trial