Zapier Glossary

• Zapier: An integration platform that connects over 6,000+ web apps and APIs together into multi-step, automated, customizable workflows. When an event happens in one app, Zapier can tell another app to perform (or do) a particular action.
• Zap: An automated Zapier workflow that connects your app to others that have built integrations. 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.
• Trigger: The app integration event that starts a Zap when new or updated data is added to your app, either by Zapier polling a specific API endpoint to check for new data or via a notification REST webhook from your app that pushes new data to Zapier.
• Action: The app integration step that finds, creates, or updates data in your app using a GET, PUT or POST request to your API using data provided when a Zap is triggered by an event in another app.
• Create action: The app integration step that creates or updates a single item in your app through an API call.
• Search action: The app integration step that finds existing data in your app, optionally with a create action to add an item if the search does not return a result.
• Task: An action that a Zap successfully completes will count towards task usage. The number of tasks a user has depends on their Zapier pricing plan.
• Zap editor: The user interface where end users build their Zaps, adding triggers and actions built by app integration developers.
• Zap history: An end user’s log of all the Zaps that have run live, showing the data going in and out of each step, any error messages and task usage.
• Filter: A built-in Zapier function that users can add to their Zap to restrict it to run only when certain conditional values contain specific data.
• Paths: A built-in Zapier function that users can add to their Zap to combine Filters and Actions 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.
• Formatter: A built-in Zapier function users can add to their Zap to customize and manipulate text, number and date data that is output from triggers and actions.
• Delay: A built-in Zapier function users can add to their Zap to place it on hold for a specified amount of time before the remaining actions run, in essence scheduling the action.
• Input Fields: Individual data fields are received from trigger and action steps in a Zap, and mapped into subsequent steps’ by a user to send that data as inputs to those steps’ destination API.
• Beta: If your app is published in the Zapier App Directory, it will remain in Beta for 90 days to indicate its newer status to end users.