Zapier is a tool that helps you automate repetitive tasks between two or more apps—no code is necessary with its user-friendly interface. When an event happens in one app, Zapier can tell another app to perform (or do) a particular action. To work with Zapier there are a few key terms to be familiar with. Let us have a look at the frequently used terms you would come across when setting up your integrations over Zapier.
Frequently Used Terms
App: This refers to any application you may be using. This can be the software you use as your CSM or mailing (e.g., HubSpot, Mailchimp) or event applications (e.g., Eventbrite, Brella)
Trigger: A trigger is an event that starts a Zap. Your integration will be based on this trigger. e.g., these can be set as when a registrant sign-up for the event, or when an invite is created in Brella.
Action: an action is what your Zap does for you when the trigger happens. Examples of actions can be adding them to a Google sheet or creating a new contact in your CSM.
Zap: This is what Zapier calls a single integration. You might hear us refer to “Building a Zap”, or “Your Zap will run” from now on. A Zap is an automated workflow that tells your apps to follow this simple command: "When this happens, do that." Every Zap has a trigger and one or more actions.
Task: When a Zap runs, each action it completes counts as one task.
Template: Zap Templates are ready-made integrations or Zaps with the apps and core fields pre-selected, for publicly available Zapier integrations. In a few clicks, you can discover a use case, connect apps, and turn on the Zap. Zap Templates are the fastest way to automate workflows.
To learn more about Zapier refer to their quick start guide for more information.