In Zapier, only successful actions count toward your task usage. Below you'll find a more detailed explanation of what counts as usage.
What are Zaps, triggers, actions, and tasks?
- A Zap is an automated workflow that you create to connect your apps.
- A trigger is an event that starts your Zap.
- An action is an event that happens after your Zap is triggered.
- A task is any successful action that a Zap performs.
What counts toward task usage
The following use one task when your Zap runs:
- All successful action steps.
- Each Filter step where the filter conditions are met.
- Each Path step where the path’s rules are met.
- In Sub-Zaps:
- Each action step within the Sub-Zap.
- The Call a Sub-Zap action step in the Zap.
- The Return From a Sub-Zap action step in the Zap.
In search actions, you can decide whether the Zap should proceed if nothing is found. If you select:
- Yes, the search action will use 1 task.
- No, the search action won’t use any tasks.
What doesn't count toward task usage
The following does not use tasks when your Zap runs:
- All trigger steps. Learn more about triggers and tasks
- Each Filter step where the filter conditions are not met.
- All action steps that error or halt.
- Each path step where the path's rules were not met.
- All subsequent action steps in the path group.
- All steps that do not run, either because a previous filter or path condition was not met or because the Zap errored.
- In Sub-Zaps, the Start a Sub-Zap trigger.
You have a Zap that:
- Triggers when a new email with an attachment is received in Gmail.
- Uploads the attachment to dropbox.
- Sends a direct message in Slack with a link to the newly uploaded file.
Uploading the file to Dropbox and sending a message in Slack automates two tasks. If your Zap runs when you receive ten emails, it will use twenty tasks.
Triggers and tasks
Zap triggers never use any tasks. A Zap's first step is always a trigger. Polling triggers will poll an app, or check for new trigger events, at a regular interval, but these polls never use any tasks.
You have a Zap that polls Facebook every two minutes to check for new leads, then sends them to your CRM app. If your plan has a two minute polling interval, Zapier will check Facebook for new leads five times in a ten minute period (every two minutes). If the Zap finds two new leads during that ten minute period, two tasks will be used when those leads are successfully sent to the CRM.
If a Zap polls an app every two minutes, this means it'll complete over twenty thousand polls per month. Zapier doesn’t charge you for these events.
Task limits and pricing
The number of tasks your account can use depends on the pricing plan you select. For plans that do not include metered tasks, Zapier will email you when you reach 80% of your task limit, and again when you reach your task limit. Once you reach your monthly limit, Zapier will hold any new Zap runs until your billing cycle resets.
If you don't want to wait for the end of the billing cycle to replay held Zap runs, you can upgrade your plan. This resets your account’s task usage. You can then manually replay Zap runs.
Monitor task usage
Task usage is based around your billing cycle. In your billing and usage settings, you can see how many tasks your Zaps have used in your current cycle, and how many days you have left until your task limit resets. Tasks are not carried over to other billing cycles.
If you're an owner or super admin on a Company plan, or an owner of a Team plan, you can export information about your account usage broken down by account member.
- Go to your member settings.
- In the upper right, click Export member data.
- A system popup window will prompt you to download and save the CSV file.
The file contains the following information for the current billing cycle:
- The names and email addresses of all members of your account.
- Their member role in your Zapier account.
- The number of Zaps they have turned on.
- The number of tasks they've used.
You can view all the tasks your Zaps attempted in your Zap history. Learn more about Zap history.