Useful to know

Zapier

Zap

A Zap is an automated workflow between your apps. For example, you may have a Zap that saves your Gmail attachments to Dropbox and another Zap that saves emails that you star in Gmail to a text file. Zaps consist of at least two parts: a trigger and one or more actions.

Trigger

A trigger is the event in an app that starts the Zap. Once you set up a Zap, Zapier will monitor the app for that event. For the save Gmail attachments to Dropbox example, you can receive a lot of emails through your Gmail account, but the Zap isn't triggered until an email contains an attachment.

Action

An action is the event that completes the Zap. For the save Gmail attachments to Dropbox example, the action is uploading the attachment from your email to Dropbox.

Task

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. You can find more details here

This information will allow you to choose the right Zapier Pricing Plan, based on your expected system load, considering the fact that every Inbound call or Outbound call will consume at least one task per each call depending on the flow you defined.