Use Webhooks to Send SMS Notifications via Zapier


Subscribe Pro Webhooks can be connected to Zapier and used to trigger a wide variety of actions and activities. We have documented an example here of how Subscribe Pro webhooks can be used to trigger SMS messages to your customers at certain points during the subscription lifecycle.

Steps

  1. In Zapier, click the “Make a Zap” button at the top left of the screen.
  2. Under "When this happens…” select “Webhooks by Zapier.” (If it isn’t listed by default, use the search bar.)

    First step of Zap creation with arrow pointing to Webhooks by Zapier.

  3. Choose “Catch Hook” as the Trigger Event and click “Continue.”

    Selecting Catch Hook from the dropdown selector under Choose Trigger Event.

  4. Copy the Custom Webhook URL, store it for future reference, and click “Continue.”

    The Custom Webhook URL that displays after step 3, with an arrow pointing to Copy.

  5. Under "Find Data," click “Test Trigger” and then “Skip Test.”

    Big blue Test Trigger button under Find Data.

    The gray Skip Test and blue Test trigger buttons that display after the previous Test trigger button is clicked.

  6. Under “Do this…” select the app that you would like to act when a Subscribe Pro webhook is caught. Proceed by logging in to your account for the selected app. (Here, we’ll be using Twilio to send an SMS text when the status of a subscription has changed.)

    The Twilio app selected under the Do this section of the Zap with Send SMS as the action event.

  7. In order to retrieve sample data to test the webhook, log into Subscribe Pro, and select the environment for which you intend to use this Zap. Then, navigate to System > Webhook Endpoints and click “+New.”

    Subscribe Pro WebHook Endpoints page with arrows pointing to the environment selector and the blue New button.

  8. Paste the Custom Webhook URL that you copied from Zapier into the Endpoint URL field. For this example, we will only be leaving the “subscription.status_change” event checked. Feel free to select any or all events, or even create different Zaps for different events (subscription status change, cancelled subscription, etc.) for more customizable and modular notifications. When finished, click “Save.”

    The custom webhook URL from step 4 pasted into Subscribe Pro's New Endpoint page.

  9. Click the “Enable” and “Test Connection - Ping Endpoint” buttons (in that order) to confirm that the URL is working properly.

    Subscribe Pro Webhook Endpoints page with an arrow pointing to the Test Connection - Ping Endpoint button.

  10. Open a new browser tab/window and go to your store website that corresponds with the environment you selected in Subscribe Pro. Log in as a sample user (or create one now). Change something that is relevant to one of the Subscribed Events you selected. Since we’re focusing on a subscription status change for this example, we logged in as a sample user to the M2 sandbox site we selected in Subscribe Pro and paused a subscription.
  11. Go back to Zapier. Scroll up to Catch Hook > Find Data (skipped). Click “Test trigger.”

    The When this happens section of the Zap with gray Test trigger and blue Continue buttons.

  12. You should see all of the webhook data for the customer based on the change made in step 10:

    Webhook data in Zapier under the Find Data section of When this happens.

  13. Click “Continue” and scroll back down to the app you chose to use the webhook data.
  14. Since we are using Twilio for this example, we will need the customer’s phone number, which can be extracted from the webhook data. (You will likely need to click “Show All Options” and scroll through all the data.)

    Customizing the Twilio SMS recipient number in Zapier using the Subscribe Pro webhook data.

  15. Next, we will be composing the body of our template SMS message. Click “Continue” when finished.

    Composing the Twilio SMS body in Zapier using the Subscribe Pro webhook data.

  16. After customizing the entire SMS message, we can preview it. Click “Test & Continue” to ensure that the message goes through and appears the way you’d like it to.

    The preview of the custom SMS in Zapier with gray Test & Review and blue Test & Continue buttons.

  17. The SMS message should go through immediately (Note: Since we are only using a Twilio trial account for the purposes of this example, the message “Sent from your Twilio trial account - ” will precede all of our SMS texts.)

    Screenshot from an iPhone showing what the SMS looks like once it is received.

  18. Finally, once you are content with everything, turn on the Zap and be sure to give it a name. You have successfully set up a Zap using Subscribe Pro’s webhooks.

    The Zap in Zapier with arrows pointing to the name of the Zap and the green On switch.

  19. (Optional) Repeat this process for any other subscription events. (In our example, we might repeat the process for a created subscription, cancelled subscription, changes to a customer’s payment profile, etc.)

    The Subscribed Events that can be customized in Subscribe Pro when editing or creating a webhook endpoint.