Easily Integrate Campaign monitor Webhooks with your application.
https://www.campaignmonitor.com/api/webhooks/
Steps to receive Campaign monitor Webhooks
- Sign up for your free Hooky account.
- Create a new Webhook Source, and select Campaign monitor. This will be the endpoint that receives webhooks on behalf of your application, and forwards them using the unified SDK.
- Step 1
- Step 2
- Once a webhook is received from Campaign monitor, you'll see it under the Live Logs section of your webhook source.
- Next, follow the examples below to integrate the Hooky SDK in ruby or javascript, and start receiving webhooks.
Integrating Campaign monitor Webhooks Using Javascript
- Sign up for your free Hooky account.
- Create a new Webhook Source, and select Campaign monitor. This will be the endpoint that receives webhooks on behalf of your application, and forwards them using the unified SDK.
- Step 1
- Step 2
- Once a webhook is received from Campaign monitor, you'll see it under the Live Logs section of your webhook source.
- Next, follow the examples below to integrate the Hooky SDK in ruby or javascript, and start receiving webhooks.
Integrating Campaign monitor webhooks with Hooky in your Javascript based application is straight forward. Just grab the SDK, and call a function when that webhook is received.
Integrating Campaign monitor Webhooks Using Ruby
Integrating Campaign monitor webhooks with Hooky in your Ruby or Ruby on Rails application is straight forward. Just grab the SDK, and call a method when that webhook is received.
Configuring Campaign monitor Webhook Authentication
Here's how it works
Supported Campaign monitor Webhook Events
Subscribe
When someone subscribes to one of your lists, we’ll submit an HTTP POST request similar to the following, to any URLs you’ve registered with the “Subscribe” event.
Update
When a subscriber’s details are updated, we’ll submit an HTTP POST request similar to the following, to any URLs you’ve registered with the “Update” event.
De-activate
When a subscriber in your list is de-activated, we’ll submit an HTTP POST request similar to the following, to any URLs you’ve registered with the “Deactivate” event.