Whenever your Zap successfully completes an action, it counts as a task. Trigger steps do not count as tasks, but successful action steps do. You can see all the tasks your Zaps have attempted in Zap History.
Learn about tasks in ZapierLast updated:
The following count as tasks when your Zap runs:
- Any successful action step.
- Any filter step that passes.
- Any time a path's rules pass.
- For Sub-Zaps, the Call a Sub-Zap action and the Return From a Sub-Zap action each use 1 task.
If Should This Step Be Considered a "success" When Nothing Is Found? is selected in a search step, the search action will count as a task.
The following do not count as tasks:
- Trigger steps.
- Filter steps that do not pass.
- Any step that errors or halts.
- Any path group that did not run because the path's rules were not met.
- Any step that does not run, either because a previous filter didn't pass or because the Zap errored.
- For Sub-Zaps, the Start a Sub-Zap trigger uses no tasks.
You have a Zap set up to trigger whenever you receive a new email with an attachment from Gmail, which then uploads the attachment to Dropbox, then sends you a direct message in Slack with a link to the new Dropbox file.
Each time you receive a new email with an attachment and your Zap uploads the attachment and sends you a direct message, it automates 2 tasks. If your Zap runs 10 times for 10 emails you receive, it automates 20 tasks.
Each pricing plan has different limits on the number of tasks your Zaps can automate in a given billing cycle. Zapier sends notifications when you reach 80% of your task limit, and then again when you reach your full task limit. At that point, Zapier will hold new Zap runs.
Your task limit is based on your billing cycle. In your billing and usage settings, you can see how many tasks your Zaps have used in your current billing cycle, and how many days you have left until your task limit refreshes.
You can view all the tasks that your Zaps have attempted in your Zap history.
Need more help?