A Zap is an automated workflow that connects your apps and services together. Every Zap consists of a trigger step (“when this happens…”) and one or more action steps (“then do this…”).
To start your integration first you must have clear what scenario you want to integrate and what is your role.
When you first set up your Zap trigger, Zapier will attempt to find some sample 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 a sample row. The sample row can then be used as test data in an action step later in the Zap.
Account Type: Vendor
Action: Fill Fulfillment Parameter
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.
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.
To build your workflow, Zapier provide a set of tools that allows you to manage the course of the flow
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 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. Learn more about using paths in Zaps.
Zap Multi-path example
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. Multi-step Zaps are not available on a free Zapier plan.
Zap Multi-step example
Once you finish building your integration, you can test it using the options TEST & REVIEW or TEST & CONTINUE
Not only you can test if the integration haven’t any error, you can analyze the output of the response of every step if is the expected data.
Once you had test your integration, you run it. If the integration is not in the instant mode, you can run manually or wait until Zapier runs the integration.
Zapier will check for new data from your trigger every 1 to 15 minutes in order to start your workflow, depending on your subscription plan.
Zapier relies on a few methods to make sure that your Zap does not trigger multiple times for a single new item. Learn more about how triggers are deduplicated in Zaps.
In this link you can see more information about management and administration of the integrations.