Move shared Zaps onto company-owned connections in one Team or Enterprise account before more teams build, and put an owner's name on each one. Then review changes to shared Zaps, and budget AI steps and assistant calls in the same task pool as Zap actions.
When you need this
- Several teams already build Zaps on personal accounts and connections.
- Someone who built important Zaps is leaving, and nobody knows which ones they own.
- Teams want AI steps or Zapier MCP, and the task bill is about to change.
Evaluation criteria
Setup: one company account
Do builders work in a shared account with shared app connections?
Look forUse Team or Enterprise for shared connections and folder permissions on shared Zaps. Connect SAML SSO. Team allows 25 users. Enterprise allows unlimited users and adds SCIM and domain capture.
Ownership: a name on every shared Zap
Can you list who owns each shared Zap and each connection it uses?
Look forFilter Zap history by owner and check connections on the Apps page. One Reddit user inherited about 40 undocumented Zaps. Some half-worked or used abandoned tools, leaving the user afraid to change them.
Rollout: start with hand-offs that repeat
Which hand-offs happen every day or every release?
Look forChoose repeatable work with a clear trigger and countable volume. Zapier reports that Remote's three-person IT team started with help desk intake and now closes 27.5% of about 1,100 monthly tickets automatically. Okta's SupportOps Slack bot saves up to 10 minutes per escalation.
Review practice: versions and approvals
Can someone see what changed in a Zap and roll it back?
Look forCheck version retention against your rollback needs. Professional keeps 1 month, Team 6 months, and Enterprise 1 year. Enterprise adds Compare Versions and approval requests in beta. Zapier's Healthie case study describes shared agents and team folders, with approval workflows as team leads start building.
Reliability: errors reach a person
Who hears about a failed run, and when?
Look forHave an owner or super admin enable autoreplay account-wide for temporary errors. Set per-Zap error notifications. Enable flood protection to stop runaway triggers from exhausting tasks.
Cost control: a budget before scale
Does the task tier cover the next quarter, and who can change pay-per-task?
Look forSize an annual tier by successful actions per run. Set pay-per-task deliberately. A RevOps lead at a 50-person SaaS company reports paying near US$400 a month after three years as multi-step workflows increased.
Questions to ask vendors
- Which of our Zaps run on a personal connection that leaves with its owner?
- Who approves a new shared Zap that writes to a system of record?
- What share of next quarter's tasks will AI steps and MCP calls use?
- Which workflows have grown complex enough to move to code or another platform?
Red flags
- Business-critical Zaps owned by personal accounts with personal app connections.
- Nobody can say which Zaps a departing employee owns.
- Pay-per-task on with no one watching the 80% usage emails.
- A subscription opened by a former employee that still renews to an inbox no one reads, as one company owner found years later.
Products in this piece
Sources
- Official documentation
- 10
- Public source
- 3
- Zapier pricing
- Zapier pricing reference (machine-readable)
- Zapier Help: Manage your Zapier Team or Enterprise account
- Zapier Help: Replay Zap runs
- Zapier Help: How pay-per-task billing works
- Zapier Help: Admin controls for app connections
- Zapier Help: How is task usage measured in Zapier?
- Zapier case study: How Remote saves US$500K annually and automates 11M tasks (Apr 25, 2025)
- Zapier case study: How Zapier Enterprise eased the pressure on Okta's SupportOps team (Mar 7, 2025)
- Zapier case study: How Healthie saves 60+ hours a week with Zapier Agents (Nov 25, 2025)
- Reddit r/zapier: I think I just inherited a Zapier nightmare (Apr 7, 2026)
- Reddit r/zapier: Tired of Zapier breaking at 2am (May 29, 2026)
- Reddit r/zapier: I wanted to like Zapier (Sep 24, 2026)