Zapier

Zapier runs cloud workflows called Zaps. A trigger starts the workflow and action steps read or change connected applications. It is a practical shortlist for a department that wants to route form submissions into a CRM and notify the responsible person, provided its exact apps and required actions are supported.

Build around the business event

Start with one real event and confirm the connector exposes every required field. Map stable record IDs, check for an existing record before creating another, and send failures to an owner. An app appearing in the integration directory does not guarantee a particular endpoint, attachment type, or account permission.

The Free plan currently includes 100 tasks per month and two-step Zaps. Multi-step workflows, premium apps, and webhooks are paid-plan considerations. Shared connections, administrative controls, and support also vary by plan. Zapier operates under its cloud service terms.

Understand tasks before estimating cost

A successful action normally consumes a task. Triggers do not. Filters, Paths, and several built-in tools have exemptions. AI model tiers, extended code runtime, and MCP calls can have different rates. Replaying successful actions can consume tasks again, while Agents use a separate activity allowance.

Estimate your actual branching paths and record volume, then inspect task history during a pilot. Check overage billing, what happens at the limit, polling intervals, and connected-app API limits. Require approval before a generated message or record change affects a customer. A workflow subscription does not remove the subscriptions or permissions required by its connected services.

Official sources checked on October 23, 2026. Pricing, task accounting, and service terms.