Skip to content

Workflows

Build the follow-up once. It runs for every client.

Answer a lead the moment the form arrives, chase the quiet ones, remind, escalate and report. You add the steps and Thrum lays them out, so a workflow stays readable however much it grows.

Each client’s runs use that client’s own accounts and keys, and every run is kept step by step.

Get early accessSee pricing

Thrum opens soon. Sign up now and you’ll be among the first in.

Urgent enquiryOne workflow, passage by passage

A branch, then three paths at once

An urgent enquiry gets a reply with the booking link, a message to the front desk and a HubSpot record, all at the same moment. Anything else goes on a sheet.

A branch, then three paths at once on the canvas.A branch, then three paths at once on the canvas.

Scroll sideways to follow it.

A draft, a yes, a wait, a deposit

An AI step drafts the quote, a person approves it, the email goes out, and a day later the last step makes a checkout link for the deposit.

A draft, a yes, a wait, a deposit on the canvas.A draft, a yes, a wait, a deposit on the canvas.

Scroll sideways to follow it.

Branches and paths

Send each lead the right way, and do several things at once.

A branch sends the run one way or the other: an urgent job to the owner’s phone, everything else to the usual reply.

Paths at once run side by side, so the owner gets a text while the office gets an email, and the next step waits until every path has finished.

A workflow that, after its loop, runs three paths at the same time: text the owner, log it, and email the office.A workflow that, after its loop, runs three paths at the same time: text the owner, log it, and email the office.

Three paths at once

Loops

Work through a whole list in one run.

Chase every overdue invoice, follow up every lead nobody has called this week, or send each customer their own reminder. A loop runs its steps once for each item, one or two at a time.

If one item fails, it is recorded and the loop carries on with the rest.

A loop on the canvas: it looks up who is on call, then for each stylist texts them the enquiry and notes on the record who was asked.A loop on the canvas: it looks up who is on call, then for each stylist texts them the enquiry and notes on the record who was asked.

Waits and approvals

Wait an hour, wait for a reply, or wait for a person’s yes.

Pause for a set time, until a condition holds, until a form comes back, or until another system calls back. The run picks up exactly where it stopped.

An approval step stops the run and asks named people, on your team or at the client, for a yes or no. The first answer decides which way it goes. Approvals are in beta.

A run waiting on an approval: who it is waiting on, whether each person was reached, and Approve and Reject.A run waiting on an approval: who it is waiting on, whether each person was reached, and Approve and Reject.

Built-in steps

Steps that work with the rest of the product, with nothing to connect.

A step can text or email a lead inside their inbox thread, add or update a CRM record and move its stage, send a marketing email, make a checkout link, draft a post, or make a PDF. Each one already knows the client it runs for.

The canvas offers 19 built-in steps, grouped as Send, Data and Flow. Here are the core ones and what each takes.

notify

Text or email

Sends a text through the client’s Twilio account or an email through their Resend account. A message with no address is skipped, not failed.

{
  channel: "sms",
  to: "{{ lead.phone }}",
  message: "Hi {{ lead.name }}, thanks for contacting {{ template.business_name }}.",
  credential_id: "twilio: Northside Plumbing",
  max_attempts: 3
}

Connected apps

Reach the apps your clients already pay for.

37 apps, 32 with ready-made steps, and a web request reaches any other app with an API, using the client’s own key. Most app steps are in beta.

An agent step hands a model a task and only the app steps you choose. It runs on the client’s own Anthropic, OpenAI, OpenRouter or Groq key, and is in beta.

An agent step on the canvas, with the two app steps it is allowed to call.An agent step on the canvas, with the two app steps it is allowed to call.

Moving in

Bring your n8n and Make workflows with you.

Paste an n8n workflow or drop a Make blueprint. It is redrawn as steps with a report of what came across, and arrives switched off, with a to-do for anything that needs your eye.

A Make scenario imported: the steps it became and a report of what came across.A Make scenario imported: the steps it became and a report of what came across.

Schedules and triggers

Start from what happens in the business, or from the clock.

A form sent, a booking made or moved, a website chat, a record changing stage, a payment, a click in an email, or a person pressing Run. Each comes from the product itself, so there is nothing to wire up.

Schedules run in the client’s own time zone. Events in connected apps can start a workflow too (in beta).

A workflow's schedule: every weekday at 08:00, in the client's own time zone.A workflow's schedule: every weekday at 08:00, in the client's own time zone.

Runs and retries

When a step fails, fix it and carry on from that step.

A step that hits a network error, a server error or a rate limit is tried again by itself. If it still fails, the run shows the step and the error in plain words.

Fix the cause and retry from the step that failed, keeping everything that came before it, or start again from any step you pick.

A failed run: the step that failed, its error in plain words, and Retry from where it stopped.A failed run: the step that failed, its error in plain words, and Retry from where it stopped.

Specs

Workflow limits

Items in one loop
Up to 500, one or two at a time
Steps in one run
Up to 2,000
Paths at once
2 to 8
Attempts at a failing step
3, waiting 5 seconds and doubling, at most 10 minutes
A service that asks for a pause
Given it, up to an hour
Web request timeout
15 seconds, unless the step sets its own
Files in a run
Up to 4.5 MB each, encrypted, kept 30 days
Agent step
6 tools, 8 model calls, 12 tool calls, 5 minutes
Fastest scheduleEvery 5, 10, 15 or 30 minutes, hourly, daily, weekdays or chosen days
5 min on Agency and Scale, daily on Solo
App triggersIn beta
By webhook within seconds, or checked every 5 to 15 minutes
Run details kept
7 days on Solo, 90 days on Agency, 1 year on Scale

Questions about workflows

Do I build a workflow again for every client?

No. Build it once and save it as a template with the few fields that differ, such as the owner’s mobile. Each client gets their own copy on their own keys, and a new version rolls out to the clients you pick.

What about the apps my clients already use?

37 apps, 32 with ready-made steps (HubSpot, Slack, Google Sheets and Stripe among them), and the web request step reaches any other app with an API, on the client’s own key. App triggers and most app steps are in beta. The integrations page lists every app and how it connects.

How much of an n8n workflow comes across?

Of 369 public n8n templates we tried, 224 came across. Make routers become paths at once and iterators become loops. Anything that does not convert with certainty is listed, and the workflow stays off until you have checked it.

What happens if a run crashes halfway?

Each step is saved as it finishes, so a crash repeats at most the step that was running, and a text or email that may already have gone out is not sent again. A refused request fails at once, because trying again would not help.

Can a customer’s answer run as code?

No. Values from earlier in the run are read by name, in double braces, and nothing a customer types is ever run as code.

Related

Thrum is cooking.

Get early access and you’ll be among the first in. Early members get a launch perk.

Get early accessSee pricing