Easily Integrate Mailchimp Webhooks with your application.
https://mailchimp.com/developer/transactional/docs/webhooks/#event-types
Steps to receive Mailchimp Webhooks
- Sign up for your free Hooky account.
- Create a new Webhook Source, and select Mailchimp. 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 Mailchimp, 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 Mailchimp Webhooks Using Javascript
- Sign up for your free Hooky account.
- Create a new Webhook Source, and select Mailchimp. 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 Mailchimp, 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 Mailchimp 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 Mailchimp Webhooks Using Ruby
Integrating Mailchimp 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 Mailchimp Webhook Authentication
Here's how it works
Supported Mailchimp Webhook Events
ts
the integer UTC UNIX timestamp when the event occurred
event
the name of the event, one of: send, deferral, hard_bounce, soft_bounce, open, click, spam, unsub, reject
url
for click events only, the url clicked for the event
ip
for open and click events only, the IP address where the event originated
user_agent
for open and click events only, the user agent string for the environment (i.e., browser or email client) where the open or click occurred
location
for open and click events only, the geolocation where the event occurred. Value will be null if no location can be determined from the IP address of the event. Otherwise, an array of key–value pairs with the following keys:
user_agent_parsed
for open and click events only, a parsed version of the user agent detected for the event. Value will be null if the user agent can’t be determined. Otherwise, an array of key–value pairs with the following keys:
_id
the unique identifier of the message that generated the event. This is not an event identifier, but rather a reference to the message ID for the email that was sent, opened, clicked, etc.
msg
details about the message for which the event occurred. May be empty if the message that generated an open or click is older than 30 days, or when the message was not yet indexed when the event occurred.
ts
the integer UTC UNIX timestamp when the event occurred
type
the list that the sync event applies to (allowlist or denylist)
action
the name of the event. Possible values: add (allowlist or denylist), remove (allowlist or denylist), change (denylist only)
ts
the integer UTC UNIX timestamp when the event occurred
event
the name of the event
msg
details about the message for which the event occurred
raw_msg
the full content of the received message, including headers and content
headers
an array of the headers received for the message, such as "Dkim-Signature", "Mime-version", "Date", "Message-Id", etc.
text
the plain text version of the message
html
the HTML version of the message
from_email
the message sender's email address
from_name
the message sender's name
to
the email addresses and names of the recipients of the message
the email address where Mailchimp Transactional received the message
subject
the subject line of the message
tags
the tags applied to the message; inbound messages won’t have tags, since they’re being received instead of sent, so this should always be an empty array
sender
In inbound, sender will always show as null
attachments
an array of attachments for the message, with filenames as keys. If there are no attachments, this key is omitted. Each attachment has the following keys:
images
an array of images for the message, with filenames as keys. If there are no images, this key is omitted. Each image has the following keys:
spam_report
the results of processing the message with the default SpamAssassin rules. Contains the following key:
matched_rules
an array of objects containing details about the rules that the message matched. Each rule entry contains the following keys:
spf
SPF validation results, or null if an error occurred while checking SPF for the message. Contains the following keys: