RudderStack lets you add any source that supports a webhook and use it to send events to your preferred destinations.

You can configure webhooks as sources only for the platforms that support them.

Getting started

Follow these steps to set up your webhook source in the RudderStack dashboard:

In this example, events are ingested from Mailchimp into RudderStack by configuring a webhook.
  1. Go to your RudderStack dashboard and click Add Source. From the list of Event Streams sources, select Webhook.
  2. Assign a name to your source and click Continue.
  3. Your webhook source is now created. Note the Webhook URL containing the Write key as a query parameter, as shown:
Webhook endpoint
  1. Then, add a destination in RudderStack and connect it to this webhook source.
For this example, Google Analytics is configured as a destination.
  1. Next, add the webhook URL to your source platform - in this case, Mailchimp.
You can configure webhooks as sources only for the platforms that support them.

The following image shows the webhook URL added in Mailchimp:

Adding the webhook to an event source
Add and test your webhook URL. You can use the Live Events functionality to view the events tracked in real time.

When the users perform any action configured in the source, the source platform will automatically send the generated events to the webhook URL.

In this example, Mailchimp sends the updates under Trigger on Events (seen in the above image) as the user events to the webhook URL with the content type application/x-www-form-urlencoded.

The content type can vary in case of the other webhook sources.

RudderStack then takes the data, creates the payload, and sends it to the destinations connected to the webhook source (Google Analytics, in this case).

You must also add the appropriate Transformation to transform the payload into a destination-specific format before sending it to the destination. Refer to the Payload creation and transformation section for more details.

Payload creation and transformation

This section details how RudderStack receives the data from the webhook source platform and creates the resulting payload.

  1. Continuing with our Mailchimp example, suppose a customer subscribes to Mailchimp. Mailchimp then sends the following data to RudderStack:
  1. RudderStack receives this data and creates the following payload:
type: "track",
event: "webhook_source_event",
rudderId: "044448e2-a674-426c-ba61-8341262babcc",
messageId: "4379907d-689a-4e3a-a2f7-477e29a02299",
properties: {
type: ["subscribe"],
"data[id]": ["e2ff089583"],
fired_at: ["2021-07-28 08:06:59"],
"data[email]": ["[]("],
"data[ip_opt]": [""],
"data[web_id]": ["161912900"],
"data[list_id]": ["ec4689c266"],
"data[email_type]": ["html"],
"data[merges][EMAIL]": [
"data[merges][FNAME]": ["Name"],
"data[merges][LNAME]": ["Surname"],
"data[merges][PHONE]": [""],
"data[merges][ADDRESS]": [""],
"data[merges][BIRTHDAY]": [""],
anonymousId: "d6597ba2-54db-4bd7-8769-86ac067b4178",
  1. Transform this payload as per the event format accepted by destination. To do this, use RudderStack's Transformation feature. A sample transformation is as shown below:
export function transformEvent(event) {
const updatedEvent = event
const { properties } = event
if (properties) {
updatedEvent.event = properties.type
updatedEvent.userId = properties["data[email]"] = `${properties["data[merges][FNAME]"]} ${properties["data[merges][LNAME]"]}` = properties["data[merges][PHONE]"]
return updatedEvent

The transformed payload is shown below:

type: 'track',
event: [
rudderId: '044448e2-a674-426c-ba61-8341262babcc',
messageId: '4379907d-689a-4e3a-a2f7-477e29a02299',
properties: {
type: [
'data[id]': [
fired_at: [
'2021-07-28 08:06:59'
'data[email]': [
'data[ip_opt]': [
'data[web_id]': [
'data[list_id]': [
'data[email_type]': [
'data[merges][EMAIL]': [
'data[merges][ADDRESS]': [
'data[merges][BIRTHDAY]': [
name: 'Name Surname',
phone: [
anonymousId: 'd6597ba2-54db-4bd7-8769-86ac067b4178',
userId: [
  1. RudderStack then sends this payload to the destinations connected to your source - Google Analytics, in this case.

Contact us

For more information on the topics covered on this page, email us or start a conversation in our Slack community.

On this page