Zapier empowers businesses to create processes and systems that let computers do what they do best - automating information transfer, allowing humans to be more productive.
The first step is to make sure Zapier supports the source type and connection mode you’ve chosen to implement. You can learn more about what dictates the connection modes we support here.
- Navigate to your Zapier dashboard and select “Make A Zap” - you’ll need at least one Zap so you can tell Segment where to route data later on.
Search “Webhooks”, then select “Catch Raw Hook” (Segment POSTs raw data to Zapier via our destination).
- Complete the remaining Webhook setup steps, and Zapier will present you with a custom Webhook URL.
- Repeat step 3 to create as many Webhook URLs as you like.
Remember that each Zapier “trigger” should be connected to an “Action” - i.e. posting the Webhook data to another downstream tool, such as Slack.
- From your Segment UI’s Destinations page click on “Add Destination”.
- Search for “Zapier” within the Destinations Catalog and confirm the Source you’d like to connect to.
- Add your custom Webhook URLs to your destination settings as desired.
- Starting sending data!
Page / Screen
Segment doesn’t perform any transformations or mappings on data you send to Zapier - we send raw payloads. When you specify a “Zap” URL, Segment will send all your
screen events to that Zapier URL. If you also specify any “Page/Screen Zaps” under “Optional Settings” in your Segment settings UI, Segment will send these named
screen events to the specific Webhook URL instead of to the “Zap” URL.
When you specify a “Zap” URL, Segment will send all your track events to that Zapier URL. Leave this setting blank if you do not wish to send all track events to Zapier. As with page/screen events, Segment does not perform any transformations or mappings. If you also specify any “Event Zaps”, Segment will send these events to the specific Webhook URL instead of to the “Zap” URL.
For user-property destinations, an identify call will be sent to the destination for each user being added and removed. The property name will be the snake_cased version of the audience name you provide with a true/false value. For example, when a user first completes an order in the last 30 days, we will send an identify call with the property
order_completed_last_30days: true, and when this user no longer satisfies we will set that value to
When the audience is first created an identify call is sent for every user in the audience. Subsequent syncs will only send updates for those users which were added or removed since the last sync.
Segment lets you change these destination settings from your Segment dashboard without having to touch any code.
Enter the Zaps you want page/screen events to go to. Enter an page/screen name on the left, and a Zap URL on the right.
Enter the Zaps you want track events to go to. Enter an event name on the left, and a Zap URL on the right.
The default Zap URL events and page/screen should be sent to.
Questions? Problems? Need more info? Contact us, and we can help!