Call Zapier

The Call Zapier Action enables your app to interact with Zapier by triggering workflows that have been set up in Zapier. By configuring this action, you can automate tasks such as sending emails, creating records in external systems, or any other workflow that has been created in Zapier.

Note: Before using this action, ensure that you have set up a Zap in Zapier. The Zap should define the workflow you want to trigger (e.g., sending an email, updating a database, etc.).

For detailed instruction on how to create a zap, refer to this source https://zapier.com/blog/get-started-with-zapier/

Properties and Explanation

To configure the Call Zapier Action, you'll need to define the following properties:

1

Type of Request

This property specifies the type of HTTP request that will be made to the Zapier Webhook. Choose one of the following options depending on your Zap configuration:

• GET: Retrieve data from a remote service.

• PUT: Update existing data in a remote service.

• POST: Send new data to a remote service or trigger a workflow.

• DELETE: Remove data from a remote service.

2

URL

This is the Zapier Webhook URL that you will use to trigger your Zap. The URL should be provided by Zapier when you set up the Zap. This URL will be the endpoint to which the HTTP request is sent.

3

Body

The Body is the data you want to send to Zapier to trigger the workflow. This can be dynamic and passed as variables or static text.

The Body is the data that will be sent to Zapier in stringified JSON format. In this format, data is passed as a string, with single quotes used for the keys and values. Dynamic variables (such as user input or values from Workmaster) are represented with the &variable_name format, while static text is wrapped in single quotes.

Here’s an example of how to format the Body using stringified JSON:

"{'name': &UserName, 'email': &Email, 'subject': 'Welcome to Our App!', 'message': 'Thank you for signing up!'}"

• &UserName and &Email are dynamic variables that will be replaced with the values from the form fields or other dynamic sources in your Workmaster app.

• 'Welcome to Our App!' and 'Thank you for signing up!' are static texts that remain unchanged when the action is executed.

Important: The Body should be formatted correctly as stringified JSON and the dynamic values must be provided by Workmaster using the Formula Editor. For detailed instructions on how to use the Formula Editor, refer to the User Manual: Formula Editor.

Example Use Case

Let’s say you want to trigger an email through Zapier when a user submits a form in your app.

1. Set Up the Zap: In Zapier, create a Zap that listens for the Webhook trigger and sends an email (using the Gmail or Mailchimp app in Zapier).

2. Workmaster Configuration:

   • Type of Request: POST (because we are sending data to Zapier).

   • URL: Pate the Webhook URL from Zapier.

   • Body: Pass the user's name, email, and other form details to Zapier to use in the email template.

Once the form is submitted in Workmaster, the Call Zapier Action will trigger the Zap, which will send an email to the user.