Run Zap

​

Node Inputs

• trigger (optional): This is an input parameter that indicates the point at which the Zap should be activated. The data connected here is not used for anything specific.
• zapier webhook url: This is the URL provided by Zapier that triggers the flow. You can find more information on how to get your Zapier trigger URL from Zapier’s help article. It should look something like https://hooks.zapier.com/hooks/catch/12345678/4abcdefb/.

​

Node Output

• zapier response json: The JSON response returned by the Zapier webhook after triggering the Zap.

​

Node Functionality

This node is designed to initiate an action or a series of actions within a Zapier flow by sending a request to a specific Zapier webhook URL. When the node is executed, it sends a signal to Zapier, signaling it to carry out the actions that you have predefined in the Zapier workflow associated with the webhook URL.

If the trigger is successful, the response from Zapier will be captured and recorded. In case the trigger fails due to any issue, such as a wrong webhook URL or network problems, an error will be raised detailing the failure.

​

When To Use

Use the Run Zap node when you want to automate processes or tasks by connecting your system with Zapier. It can be particularly useful when you have set up a sequence of automated actions on Zapier that need to be triggered by specific events or conditions in your system.

Some examples of when to use this node include:

• Sending an automated email when a user signs up for your service.
• Creating calendar events automatically from a booking system.
• Logging customer support tickets into a CRM system.

No technical experience is required for setting up the Zap on Zapier’s platform. However, determining when and how the Run Zap node should trigger the flow will depend on the workflow and business rules defined within your system.