Zapier is an online automation tool that connects your apps and services. You can connect two or more apps to automate repetitive tasks without coding or relying on developers to build the integration. This guide walks you through key concepts to help you get started with Zapier.
Zap: A Zap is an automated workflow that connects your apps and services together. Each Zap consists of a trigger and one or more actions. When you turn your Zap on, it will run the action steps every time the trigger event occurs.
Learn more about creating a Zap and managing your Zaps.
Zap Editor: The Zap editor allows you to create a Zap from scratch. In the Zap editor, you can set up a trigger and one or more actions.
App: An app is a web service or application, such as Google Docs, Slack, or Salesforce. Zapier offers integrations for over 3,000 apps, letting you move data between them or automate repetitive tasks. Explore the Apps you can connect to Zapier.
Trigger: A trigger is an event that starts a Zap. For example, if you want to send a text message each time you receive an email, the trigger is ‘new email in inbox’. Learn more about using triggers in Zaps.
Test Data: When you first set up your Zap trigger, Zapier will attempt to find some existing data from your trigger app to use in the Zap. For example, if your trigger brings in data from a new Google Sheets spreadsheet row, Zapier will pull in an existing row. The sample row can then be used as test data in an action step later in the Zap.
Action: An action is an event a Zap performs after it is triggered. For example, if you want to send a text message each time you receive an email, the action is ‘send a text message’. Learn more about using actions in Zaps.
Task: A task is an action your Zap successfully completes. For example, if your Zap has an action to create new Google Contacts, each contact that is created will count as one task.
Zap History: Your Zap History displays a log of all your Zap activity, including all the data that goes in and out of each of your Zap steps. Learn more about Zap History.
Filter: Filters can be added to any Zap to restrict it to run only when certain conditions are met. For example, if you want to send a text message each time you receive an email, you can add a filter so the Zap only runs when emails are received from a specific email address. Learn more about using filters in Zaps.
Paths: Paths let you build advanced workflows to perform different actions based on different conditions. Paths use conditional, if/then logic: if A happens in your trigger app, then perform this action, if B happens, then perform this other action, and so on.
Multi-Step Zap: A single-step Zap has one trigger and one action. If the Zap has more than one action or includes filters or searches, it is considered a multi-step Zap.
Transfer: Transfer is a beta feature that you can use to send existing data from one app to another. Transfer lets you select which data to send so you only send the data that you want. Learn more about Transfer.