Zapier vs US Tech Automations: Law Firm API Limits, 2026

The public pricing page says 150 API calls per flow per day on Growth and 50 on Solo. A legal buyer needs to know whether that sentence will run intake. Zapier bills monthly tasks and throttles bursts. Those are different units. Mixing them is how a firm buys the wrong plan.

This comparison translates one law-firm intake flow into call counts under the Growth cap and into Zapier tasks, with numbered steps to measure before anyone pays. Figures below are from pages opened September 1, 2026. Zapier monthly task-plan dollars are UNKNOWN in this outline; this article will not invent a Zapier SKU. Clio and PracticePanther rate limits are not quoted; those vendor docs were not opened for this page.

Hypothetical composite only: a litigation boutique with a web form, a practice-management system, e-sign, and a calendar is the labeled example. Matter counts below are hypothetical. They are not a customer, not a case study, and not a named firm.

Key Takeaways

• An API call on Growth is one request a single flow makes to another system in a calendar day, counted per flow, not per account. Growth allows 150 of those per flow per day as of September 1, 2026. That is not 150 Zapier tasks.

• Solo is 50 API calls per flow per day and 3 active flows at $96 per month annual; Growth is 150 and 5 flows at $372 per month annual; Scale is 500 and 10 flows at $1,371 per month annual. Performance is unlimited API calls at a custom price. All four lines are from the public pricing page as of September 1, 2026. This article does not link that page.

• Growth also allows 2 scheduled runs per day, with 3x allowed 15 days per month, on that same page. A law-firm intake that polls practice management every 5 minutes is not a "scheduled run" in that sense. Count the API calls.

• Zapier counts successful action steps as tasks per month. Instant triggers return HTTP 429 after 20,000 requests every 5 minutes per user. Free/trial polling Zaps are held after 200 requests every 10 minutes per Zap. Zaps are limited to 100 steps. Two-way sync is not supported, according to Zapier pages opened September 1, 2026.

• Pilot: one intake flow, one week, log every call. Success is a counted peak day. Kill the purchase if nobody can produce that log. Do not start on Performance custom until the log exists.

Direct answer: daily per-flow calls are not monthly tasks

On US Tech Automations, an API call is one request a single flow makes to another system in a calendar day, counted per flow, not per account. Growth allows 150 of those per flow per day as of September 1, 2026. Zapier counts successful action steps as tasks per month, and separately throttles bursts (20,000 instant-trigger requests per 5 minutes per user).

150 per flow per day is not 150 Zapier tasks. Do not convert them with a made-up multiplier. A flow that writes four systems per new matter is four calls per matter on the Growth side. On Zapier, the same work is however many successful action steps ran, billed against a monthly task bucket, with a separate burst throttle.

The homepage at Zapier (checked September 1, 2026) is the product home. Limits used here come from Zapier's published Zap-limits material opened the same date, according to Zapier. Instant triggers 429 at 20,000 requests / 5 minutes / user. Free/trial polling Zaps are held at 200 requests / 10 minutes / Zap. 100 steps per Zap. Two-way sync is not supported.

Client intake still moves confidential information. A lawyer shall not reveal information relating to the representation of a client unless the client gives informed consent or another exception applies, according to ABA Model Rule 1.6. An API call that writes a new matter into practice management is still that information in motion. Cap math does not replace a confidentiality analysis.

Law-firm cloud vendors remain a competence and confidentiality problem, according to the American Bar Association ethics materials on technology and confidentiality. This page will not turn a call budget into an ethics opinion. It will tell you whether 150 calls per flow per day is even in the neighborhood of one busy intake day.

Access control on the systems those calls touch should follow a documented baseline, according to NIST SP 800-53. Counting calls is not that baseline. It is only how you avoid buying Solo when the hot flow needs Scale, or buying Scale when the hot flow is 80.

Evaluation: unit of measure

Score fit, not a winner. Daily per-flow caps and monthly task buckets solve different failure modes.

Do not read the Growth 372 cell as "cheaper than Zapier." Zapier dollars were not opened into a SKU here.

The three published caps, plus Performance

From the public pricing page fetched September 1, 2026 (not linked here):

Ten quiet flows and one hot intake is a Growth-shaped problem, not a Scale-shaped problem, until the hot flow exceeds 150. The cap is per flow per day. Splitting one hot intake into two flows is a design choice. It is not a way to pretend 150 became 300 without looking at what each flow actually calls.

A law-firm intake that polls a practice-management system every 5 minutes is not a "scheduled run" in the Growth 2-per-day sense. Count the API calls. If each poll is a call, the arithmetic is the number of polls in a calendar day, plus writes per new matter, plus e-sign and calendar writes. Practice-management vendor rate limits are UNKNOWN here. Do not invent Clio or PracticePanther caps.

Hold-and-replay: Zapier will hold runs at the task limit, according to Zapier. The public pricing page opened September 1, 2026 does not describe a hold-and-replay behavior for the daily per-flow cap. Do not assume they match. If the hot flow exceeds 150, plan for a stop or an error you can see, not for silent replay, unless a later vendor document says otherwise.

Trust-account work is a different flow. Do not fold IOLTA transfers into the intake call budget. See how to set up a Clio trust account for that job, and do not treat those steps as extra Zapier tasks on this page.

What Zapier publishes on tasks and bursts

Task = successful action step. Triggers and filters often do not count, according to Zapier. Instant triggers 429 at 20,000 requests every 5 minutes per user. Free and trial polling Zaps are held at 200 requests every 10 minutes per Zap. 100 steps per Zap. Two-way sync is not supported.

Zapier dollar prices for a given task tier: UNKNOWN in this outline. Open Zapier's pricing page when you buy. Do not use a remembered monthly number from a screenshot that is not dated here.

If the problem is a burst — a webhook storm, a mass import, a calendar sync that fans out — Zapier's 5-minute cap is the relevant number, not Growth's daily 150. If the problem is a steady drip of new matters all day, Growth's 150 is the relevant number, not Zapier's 20,000.

A 100-step Zap is a ceiling. Intake that branches through conflicts, engagement letters, e-sign, calendar, and billing can hit it. That is a Zapier-shaped constraint. It is not an API-call-per-flow constraint.

Calendar fan-out across attorneys is its own workflow. If that is the burst you are afraid of, read calendar conflict checks across multiple attorneys as a sibling, then come back and count the calls that sibling would add. Do not guess the add.

Numbered steps to count a law-firm intake before you buy

Do this on paper for one flow. Then pick a plan.

1. List every system the flow touches (intake form, practice management, e-sign, calendar). Do not add billing yet unless billing truly runs on the same flow. Billing ROI is a sibling: law firm billing automation.

2. Count writes per new matter. A labeled hypothetical: 20 new matters times 4 writes equals 80 calls. That 20 is not a named firm's volume.

3. Multiply by a busy day's new matters. Keep the hypothetical label. If the busy day is 20 matters and writes stay at 4, the write subtotal is 80.

4. Add polling if you poll instead of webhook. Polling every 5 minutes is 288 polls in 24 hours if each poll is a call. 288 already exceeds Growth's 150 and Solo's 50. Scale's 500 would cover 288 polls with room for the 80 writes (368), still as a labeled hypothetical. Webhooks avoid that poll arithmetic. Practice-management webhook limits remain UNKNOWN here.

5. Compare the day's total to 50 / 150 / 500. US Tech Automations counts those calls per flow per day, which is why a quiet second flow does not rescue a hot first flow.

6. If over 150, split flows or move to Scale. Splitting is allowed only if each flow has a real boundary (for example, webhook intake versus nightly archive), not a fake split to dodge the cap.

7. If the burst is the problem, Zapier's 5-minute cap is the relevant number, not the daily cap.

8. Put the count in a one-page sheet. US Tech Automations writes that sheet from the week's log so the plan choice is a counted peak day, not a guess.

9. Only then pick a plan. Do not start on Performance custom until the log exists.

Matter intake design beyond call math lives in legal matter intake automation. Review-request routing is legal review requests. Neither article converts 150 calls into 150 tasks.

Hypothetical busy-day arithmetic (labeled hypothetical)

If the firm uses webhooks and not polling, drop the 288. The write subtotal of 80 fits Growth's 150 and does not need Scale, still as a hypothetical. That is why the log in the pilot matters. Guessing 288 polls you do not run is how you over-buy Scale. Ignoring polls you do run is how you under-buy Growth.

A labeled hypothetical week of logging looks like this. Day 1: 12 new matters, webhook intake, four writes each, 48 calls, no polling. Day 2: 8 matters, 32 calls. Day 3: a partner turns on a 5-minute poll "just to be safe," and the day jumps by 288 poll calls plus the writes. The peak day is now a Scale-shaped day even though matter volume fell. Day 4: poll off, back under 150. The log is what makes Day 3 visible. Without it, the firm either panics into Performance custom or stays on Growth and watches the hot flow fail on the first heavy poll.

Those day counts are hypothetical arithmetic, not a named firm's volume. Keep the label if you reuse the sheet. Replace 12 and 8 with your own intake log before you pay.

Zapier on that same hypothetical week is a different spreadsheet. Day 1's 48 writes are 48 tasks only if every write is a successful action step and nothing else ran. Filters that drop spam form fills may not count, according to Zapier. A calendar fan-out that creates five events per matter would count five action steps, not one. Do not copy the 48 into a Zapier column and call it a conversion. Build Zapier's column from Zapier's own task history after a week of a real Zap, or do not fill it.

Limitation: per-flow versus per-account, and hold behavior

The cap is per flow per day. Ten quiet flows and one hot intake is a Growth-shaped problem until the hot flow exceeds 150. Buying Scale because the account has ten flows is the wrong read of the table.

Zapier will hold runs at the task limit. The public pricing page opened September 1, 2026 does not describe a matching hold-and-replay. Do not assume overnight catch-up. Watch the log.

Do not say 150 calls equal 150 Zapier tasks. Do not quote a Zapier monthly dollar price. Do not invent Clio or PracticePanther rate limits.

Performance unlimited is a custom conversation. It is not the first purchase after a blank week.

One-week intake log before you buy

Labeled hypothetical design, not a named-firm result.

• One intake flow, one week, log every call.

• Success: a counted peak day.

• Kill the purchase if nobody can produce that log.

• Do not start on Performance custom until the log exists.

For the homepage after the log exists, use US Tech Automations. That link is not a Zapier task plan and is not a pricing-page shortcut.

FAQ

Is 150 API calls per flow per day the same as 150 Zapier tasks?

No. Direct answer: they are different units. One is a per-flow calendar-day request count. The other is monthly successful action steps, plus a separate burst throttle.

What are the three published daily caps as of September 1, 2026?

Solo 50, Growth 150, Scale 500 API calls per flow per day. Direct answer: Solo $96/month annual with 3 flows; Growth $372/month annual with 5 flows; Scale $1,371/month annual with 10 flows; Performance is unlimited at a custom price.

Does polling Clio every 5 minutes count as a Growth scheduled run?

No. Direct answer: Growth's 2 scheduled runs per day are not that poll. Count the API calls. Clio's own rate limits are UNKNOWN here.

What if our problem is a webhook storm, not a busy matter day?

Use Zapier's 20,000 instant-trigger requests per 5 minutes per user as the relevant cap. Direct answer: that burst number is not the Growth 150.

What Zapier plan should we buy, in dollars?

UNKNOWN in this outline. Direct answer: open Zapier's pricing page when you buy; this article will not invent a task-tier SKU.

How do we know we are ready to pick Growth versus Scale?

Produce a one-week log with a counted peak day. Direct answer: kill the purchase if nobody can produce that log; do not start on Performance custom first.

Does two-way sync run on either product?

Zapier does not support two-way sync, according to Zapier. Direct answer: do not buy either product as a sync engine for practice management.