Zapier Terminology

If you're not familiar with Zapier, terms like "zap" and "task" might not mean much to you. In this article, we will look at some of the key terms you need to understand to set up integrations between Member365 and other software with Zapier.

 

App: Any software or service that can be integrated with Zapier. Zapier supports thousands of apps, including Member365 and other popular ones like Google Sheets, Salesforce, Mailchimp, Zoom, and many more.

 

API: Application Programming Interface. A set of rules and protocols that allows different software applications to communicate with each other.

  • Zapier relies heavily on APIs: To perform any action within an app (like creating a new contact, sending an email, updating a record), Zapier interacts with that app's API.
  • API as the interface: The API acts as the interface between Zapier and the other application. It defines the rules and protocols for how Zapier can request information or perform actions within that app.
  • Behind the scenes: When you create a Zap, Zapier uses the APIs of the involved apps to execute each step in your workflow. For example, if you want to create a new contact in Salesforce when a new lead is submitted on your website, Zapier utilizes the Salesforce API to add that contact to your Salesforce database.

 

Zap: The core unit of automation in Zapier. It's like a recipe that defines a specific workflow between two or more apps. Think "when X happens in one app, make Y happen in another."

  • Example: "When a new contact is added to Member365, create a new deal in Salesforce, "When someone registers for an Event in Member365, create a webinar registration in Zoom."

 

Trigger: The starting point of a Zap. It's the event that initiates the automation - the X from above. Learn more about Member365 triggers in this article.

  • Examples: "New contact created in Member365," "New person joins a live webinar," "New email received in Gmail"

 

Action: The task performed by Zapier after the trigger event. It's the desired outcome of the automation - the Y from above. Learn more about Member365 triggers in this article.

  • Examples: "Create a new deal in Salesforce," "Mark as attended in Member365," "Send a welcome email via Mailchimp." 

 

Task: Each time a Zap successfully completes an "Action" step, it counts as one task. Task usage is a key factor in determining your Zapier plan costs. Think of a "task" as a single completed action within your automated workflow.

  • Examples:

    • If your Zap sends an email, that's one task.

    • If your Zap creates a new contact and then sends an email, that's two tasks.

 

Integration: The connection between two or more apps facilitated by Zapier. It allows data and actions to flow seamlessly between different platforms.

  • Examples: "Member365 is integrated with Zoom," "Member365 is integrated with Pheedloop," "Member365 is integrated with Mailchimp."

 

Step: A single action or decision point within a Zap. Zaps can have multiple steps, allowing for more complex workflows. A simple, two-step Zap has one trigger and one action. A Zap can have multiple actions or other steps such as filters, paths, delays, or searches. Only two-step Zaps are available with Zapier's Free plan, but multi-step zaps are possible and can be very valuable.

 

Filter: A decision point (i.e., condition) that determines whether a Zap should proceed or not. Filters are used to refine the automation and ensure only relevant data is processed.

  • Example: "Only proceed if the contact's country is 'United States'."

 

Path: Creates branching logic within a Zap. Allows you to define different workflows based on specific conditions.

  • Example:
    • Path 1 (if condition A is true): Send an email and update the CRM.
    • Path 2 (if condition A is false): Send a different email and log the event.
  • The key difference between a filter and a path is a filter says "only proceed if the condition is met" and a path says "if a condition is met, proceed this way, if it's not met (or a different condition is met) proceed this other way."

 

Delay: Introduces a pause or wait time between actions.

  • Example: "Wait 1 hour before sending the email."

 

Search: Allows you to find existing information within an app before proceeding.

  • Example: "Search for the contact in your CRM. If found, update their information. If not found, create a new contact."
Was this article helpful?
0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.