Every workflow starts with a trigger — on demand, on a schedule, or on an entity activity like save, approve or reject — then runs a sequence of steps: queries, API calls, reusable functions, tools and AI agents, with conditions and branches in between. No code required.
Pick how a workflow fires — a manual run, a schedule, or the moment something happens to one of your entities. This is the start node on the canvas, and it defines the whole workflow.
Fire the workflow manually — from a button on a record, a custom action, or an API call. Good for one-off runs and testing before you wire up a live trigger.
Run on a recurring schedule — hourly digests, nightly syncs, weekly reports, SLA sweeps. The clock is the trigger, no event needed.
Fire the instant something happens to a record — pick the entity, then the event.
A workflow isn't a straight line. Add conditions that evaluate field values, then split into branches so each path runs its own set of steps. Compare fields, combine rules with AND / OR, and nest as deep as your process needs.
Compare numbers, text, dates, status, dropdowns and references with operators like equals, greater-than, contains and is-empty.
Group conditions with AND / OR to express exactly when a branch should run — "high value AND new region", "overdue OR unassigned".
Each branch runs its own ordered steps. Yes goes one way, No goes another — and a single workflow handles both.
Drop steps onto the canvas and wire them together in the order they should run. A function is just a step — one that wraps reusable logic you can nest inside any workflow.
Pull a saved query into a step — no hand-written SQL, no separate data layer to maintain.
Call any REST endpoint directly, authenticated with a connector and a secret.
Call another reusable function — typed inputs and outputs, nested as deep as you need, shared across workflows.
WhatsApp, Email, Slack, Stripe and more — connectors secured by the secrets manager, called as a step.
Hand a step to an AI agent for judgment calls a rule can't make — then act on what it decides.
Only run a step when a rule matches, and decide what happens when it doesn't — stop, flag, or skip.
Wait, then continue — or repeat a step over a list of results, one at a time or all at once.
Map fields between steps and redact sensitive data before it's logged or passed downstream.
An order management process. The moment an order is marked paid, one workflow handles fulfillment routing, approvals on big orders, customer comms and the team heads-up — with zero manual steps.
The workflow's start node listens on the Order entity for an edit, captured from the Stripe payment webhook writing the status field.
On Activity · Order · On EditOrders above the threshold branch into a credit check; everything else flows straight to fulfillment.
Branch · Order total > thresholdThe order is routed through the Approval Matrix to the finance lead. The workflow waits until it's approved before continuing.
Request approvalA reusable function decrements stock and calls the warehouse REST API to create a fulfillment job, writing the tracking ref back to the order.
Function + REST connectorAn approved WhatsApp template confirms the order with tracking link, while a Slack message lands in #orders so ops sees it instantly.
Tool · WhatsApp + SlackWorkflows are the glue. They call your integrations, route your approvals, fire your messages and hand off to your agents.
The REST and connector endpoints your workflow steps call out to.
Explore →WhatsApp templates, Email and Slack — fired automatically by your workflows.
Explore →Multi-step approval routing a workflow can pause on and resume once cleared.
Explore →Agents that run on the same triggers and schedules, using tools to act on your data.
Explore →