DashboardSign inStart your trial
In this guide · BuildClose guide

Workflows

Learn how workflows start, prepare work, ask for approval, and take action.

A workflow turns a repeatable process into a set of connected steps. It can start when something happens, prepare the work, ask a person to review it, and then take an action.

Most workflows follow this shape:

Start → Prepare or decide → Review → Take action

For example: A new lead arrives → AI drafts a follow-up → a teammate approves it → the email sends.

#Build a workflow

  1. Choose what starts it. A person can run it, it can run at a regular time, or it can start when an app, table, webhook, or email provides new information. See Start a workflow.
  2. Add the steps that prepare the work. Use AI, conditions, loops, delays, or data steps to get to the right result. See Control the flow and Take action.
  3. Add a human review where the result matters. The workflow waits in the approval queue until someone approves, rejects, or edits it. Waiting for review is free.
  4. Publish and monitor it. Published workflows use the live version for new runs. See Runs & Versions.

New to Rills? Build your first workflow, or begin with a template.

#Find the right step

#Start a workflow

Choose the event that begins a run: a manual run, a regular schedule, an event from a connected app, a webhook, new table data, or an incoming email. Set up a start.

#Control the flow

Use Condition, Loop, Delay, Any, and All to decide what happens next and when. Control the flow.

#Ask for approval

Add Human Review before an action that sends, changes, or shares information. Reviewers can approve, reject, or edit the proposal from the queue or mobile app. Set up approvals.

#Take action

Use AI, Send Email, HTTP Request, Custom Code, connected-app actions, or data and file steps to do the work. Browse actions.

#Use information from earlier steps

Every step can use information from the steps before it. Use Insert data from an earlier step to choose a value; Rills fills it in for each run. Learn how to reuse data.

#Keep workflows reliable

Actions that call an external service can retry after a temporary failure. Configure retry behavior on the action when needed. To inspect a failed run, test safely, or return to an earlier published version, see Runs & Versions.

For suggestions based on past runs and approval decisions, see Learning & Insights (Professional and higher).