Compare

Thrum and Zapier, side by side.

Zapier connects thousands of apps with no code, and has tables, forms, interfaces and agents built on top. Thrum is built for running a client’s business: forms, a CRM, an inbox, booking, email and payments with the workflows between them, each client in a workspace of their own, and a portal that shows them the results.

Get early access Jump to the comparison

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

Choose Zapier if

Your automations mostly move data between SaaS apps, your client already pays for their own Zapier account, or you need an app Thrum does not reach.

Choose Thrum if

You run several clients’ businesses from one account and want the forms, records, conversations and payments in the same system as the workflows, each client kept apart, and each client shown their results under their own brand.

Feature by feature

Zapier’s side as of 1 October 2026, with sources below.

Yes
Partly
No, or not found in their docs

Zapier and Thrum, compared. Checked 1 October 2026.
Topic	Zapier	Thrum
Building
Code in a step	Yes. Code by Zapier runs JavaScript or Python.⁶	No. Reads values by name. Runs no code.
Apps	Yes. Thousands of apps without writing a request.⁷	Yes. 32 apps with actions and triggers, texts and email built in, and any API by web request.
Loops	Yes. Looping by Zapier repeats actions for each line item, up to 500 times.⁸	Yes. For each item of a list, up to 500, one or two at a time.
Branches	Yes. Paths: up to 10 branches in a group, each with its own rules.⁹	Yes. Branches on conditions, and paths that all run at once.
Schedules	Yes. Schedule by Zapier: every hour, day, week or month.¹⁰	Yes. Every few minutes, hourly, daily, weekdays or chosen days, in the client’s time zone. Every 5 minutes at most on Agency and Scale, daily on Solo.
Webhooks in	Yes. Webhooks by Zapier gives each Zap a URL to post to.¹¹	Partly. Starts from forms, bookings, chats, records, payments and email events inside the product. App triggers from 24 apps, by webhook or by checking, are in beta. No general inbound address yet.
AI agent	Yes. Zapier Agents use actions from its app library.¹²	Partly. An agent step with app actions as tools. In beta.
Knowing it works
A run that fails	Yes. Error emails, immediately or as an hourly summary, and an Alerts page.²	Yes. Degraded after 3 failures in a row or 20% of recent runs, with an email, a daily reminder and a recovery email.
A workflow that goes quiet	No. Its help centre explains why a Zap may not trigger. We found no setting that alerts you when one stops.³	Yes. Learns each workflow’s usual gap and calls it Stopped after 3 times that gap of silence.
Client delivery
Forms, CRM, inbox, booking, email, payments	Partly. Forms and tables are built in; the rest through integrations with other tools.⁷	Yes. Forms, CRM, inbox, booking, email campaigns, a blog, a newsletter and payments, built in. Several are in beta.
One workspace per client	Partly. Shared folders and app connections on Team and Enterprise.⁵	Yes. Each client is its own workspace, with its own keys, forms, workflows, CRM and portal.
A portal for the client	Partly. Interfaces, with a client portal template.⁴	Yes. A portal per client in their colours: leads, their month, inbox, bookings, email, content and revenue. White-label on Agency and Scale.
A monthly report to the client	No.	Yes. Emailed to each client on the 1st, in their time zone, and kept in their portal.
Install a set of workflows into a client	No.	Yes. A pack installs several workflows and forms into one client, switched off until each is set up.
Proposal to a running client	No.	Yes. A proposal the client accepts with an emailed code; their workspace, pack and portal set themselves up.
Bill the client for what they used	No.	Partly. Each client invoiced monthly for their texts and emails, from your own Stripe, with no cut. In beta.
Price
Priced by	Tasks: each successful action in a Zap.¹	Per seat: each seat carries a number of clients, workflow runs, forms, responses, records and emails.

Building

Code in a step: Zapier
Yes. Code by Zapier runs JavaScript or Python.⁶
Thrum
No. Reads values by name. Runs no code.
Apps: Zapier
Yes. Thousands of apps without writing a request.⁷
Thrum
Yes. 32 apps with actions and triggers, texts and email built in, and any API by web request.
Loops: Zapier
Yes. Looping by Zapier repeats actions for each line item, up to 500 times.⁸
Thrum
Yes. For each item of a list, up to 500, one or two at a time.
Branches: Zapier
Yes. Paths: up to 10 branches in a group, each with its own rules.⁹
Thrum
Yes. Branches on conditions, and paths that all run at once.
Schedules: Zapier
Yes. Schedule by Zapier: every hour, day, week or month.¹⁰
Thrum
Yes. Every few minutes, hourly, daily, weekdays or chosen days, in the client’s time zone. Every 5 minutes at most on Agency and Scale, daily on Solo.
Webhooks in: Zapier
Yes. Webhooks by Zapier gives each Zap a URL to post to.¹¹
Thrum
Partly. Starts from forms, bookings, chats, records, payments and email events inside the product. App triggers from 24 apps, by webhook or by checking, are in beta. No general inbound address yet.
AI agent: Zapier
Yes. Zapier Agents use actions from its app library.¹²
Thrum
Partly. An agent step with app actions as tools. In beta.

Knowing it works

A run that fails: Zapier
Yes. Error emails, immediately or as an hourly summary, and an Alerts page.²
Thrum
Yes. Degraded after 3 failures in a row or 20% of recent runs, with an email, a daily reminder and a recovery email.
A workflow that goes quiet: Zapier
No. Its help centre explains why a Zap may not trigger. We found no setting that alerts you when one stops.³
Thrum
Yes. Learns each workflow’s usual gap and calls it Stopped after 3 times that gap of silence.

Client delivery

Forms, CRM, inbox, booking, email, payments: Zapier
Partly. Forms and tables are built in; the rest through integrations with other tools.⁷
Thrum
Yes. Forms, CRM, inbox, booking, email campaigns, a blog, a newsletter and payments, built in. Several are in beta.
One workspace per client: Zapier
Partly. Shared folders and app connections on Team and Enterprise.⁵
Thrum
Yes. Each client is its own workspace, with its own keys, forms, workflows, CRM and portal.
A portal for the client: Zapier
Partly. Interfaces, with a client portal template.⁴
Thrum
Yes. A portal per client in their colours: leads, their month, inbox, bookings, email, content and revenue. White-label on Agency and Scale.
A monthly report to the client: Zapier
No.
Thrum
Yes. Emailed to each client on the 1st, in their time zone, and kept in their portal.
Install a set of workflows into a client: Zapier
No.
Thrum
Yes. A pack installs several workflows and forms into one client, switched off until each is set up.
Proposal to a running client: Zapier
No.
Thrum
Yes. A proposal the client accepts with an emailed code; their workspace, pack and portal set themselves up.
Bill the client for what they used: Zapier
No.
Thrum
Partly. Each client invoiced monthly for their texts and emails, from your own Stripe, with no cut. In beta.

Price

Priced by: Zapier
Tasks: each successful action in a Zap.¹
Thrum
Per seat: each seat carries a number of clients, workflow runs, forms, responses, records and emails.

Using both

A Thrum web request step can call a Zapier webhook, so a client’s workflow can hand a step to Zapier and still be watched, reported on and shown in the client’s portal.

Sources, checked 1 October 2026

Statements about Zapier were read on 1 October 2026 from search results that quote its public help pages, linked below. Plans and limits change, so check the linked page before relying on a figure.

Zapier’s own terms decide whether one account can run Zaps for several clients. Read them for your case; this page is not legal advice.

If anything here about Zapier is out of date, write to hello@thrum.run and it will be corrected.

Thrum is cooking.

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

Get early access See pricing