Zapier is an online tool that allows you to automate workflows without having to write any code. You can configure a workflow to notify your support staff via email, Slack, or other apps when Rainforest sends webhooks.

Workflows

---

Some workflows that your support staff may need to be notified for if you have not completed an automated integration to notify your merchants include:

1. Merchant application moves to the Needs Information status and requires additional verification for merchant onboarding
2. Chargeback moves to the Inquiry Action Required or Dispute Action Required status and you should work with your merchant to dispute the chargeback

Merchant application example

---

In this guide, we'll walk through how to setup a Zap to listen to Rainforest webhooks and send an email when a merchant application moves to the Needs Information status.

1. Create a Zap in Zapier.
2. Set the Trigger to Webhooks and choose "Catch Hook" as the Trigger event.

3. Copy the Zapier webhook URL.

4. In the Rainforest Sandbox Platform Portal, go to the Webhooks tab and add an endpoint. Set the Endpoint URL to the Zapier webhook URL and subscribe to the merchant_application.needs_information event.

5. Trigger the webhook by simulating a merchant application status change in the Rainforest Sandbox environment. This allows you to configure the Zap accurately in the following steps. In a later step we'll setup the webhook in the Rainforest Production environment.

6. Once a webhook has been triggered and successfully sent to the Zapier webhook, click the "Test trigger" button in your Zap. The webhook payload should populate in "request A". Continue with selected record.

7. The Action could be any app integration your platform supports, such as Slack to post to a specific channel or Zendesk to create a support ticket. In this example, we will create an Email Action. Choose the Email App and the "Send Outbound Email" Action event.

8. Configure the email contents with context from the webhook payload (populated from Steps 5 and 6 - if you do not see suggestions, then go back and test the webhook trigger). In this example, the subject line includes the merchant's name and the body includes the merchant ID, merchant application ID, and email. Add any helpful context for your support staff.

9. Test the Action of sending an email with the webhook data.

10. Check your email for the test.

11. If the email looks good, then publish your Zap!

12. Now let's update the webhook to trigger from Production instead of Sandbox. Head over to the Rainforest Production Platform Portal and configure the same Zapier webhook URL.

12. Once the webhook is configured in Production, delete the webhook from the Rainforest Sandbox Platform Portal.

12. Your Rainforest Webhook Zap is ready to go! All merchant_onboarding.needs_information webhooks will trigger an email as long as the Zap is enabled.