--- "@context": https://schema.org "@type": TechArticle "@id": https://www.twilio.com/docs/segment/connections/destinations/catalog/actions-zapier#article headline: Zapier (Actions) Destination description: Connect the Zapier (Actions) destination to send Segment events to Zaps, automate workflows, and filter events with FQL across 8,000+ app integrations. url: https://www.twilio.com/docs/segment/connections/destinations/catalog/actions-zapier inLanguage: en dateModified: 2026-06-09T02:36:11.000Z author: "@type": Organization name: Twilio Developer Education Team publisher: "@type": Organization name: Twilio --- # Zapier (Actions) Destination ## Destination Info * Accepts [Page](/docs/segment/connections/spec/page), [Alias](/docs/segment/connections/spec/alias), [Group](/docs/segment/connections/spec/group), [Identify](/docs/segment/connections/spec/identify), [Track](/docs/segment/connections/spec/track) calls. * Refer to it as **Zapier (Actions)** in the [Integrations object.](/docs/segment/guides/filtering-data/#filtering-with-the-integrations-object) * This integration is **partner owned.** Please reach out to the partner's support for any issues. * This destination is **Beta.** [Zapier](https://zapier.com/?utm_source=segmentio\&utm_medium=docs\&utm_campaign=partners) unlocks transformative AI to safely scale workflows, agents, and MCP with the world's most connected ecosystem of 8,000+ integrations. This destination is maintained by Zapier. For any issues with the destination, [contact their Support team](https://zapier.com/app/get-help). ## Getting started 1. From your workspace's [Destination catalog page](https://app.segment.com/goto-my-workspace/destinations/catalog) search for "Zapier". 2. Select **Zapier (Actions)** and click **Add Destination**. Alternatively, you can create the Zapier (Actions) destination from Zapier using the **Create Destination Zapier Action**. 3. Select an existing Source to connect to Zapier (Actions). 4. In your Zapier account, create a new Zap with the Twilio Segment - New Event trigger. 5. Configure the Zap as needed and provide a sample event payload that represents what you expect to receive from the source. To easily identify the mapping, you can provide a [Zap Identifier](#zap-identifier). 6. When you test the Zap, you will see an event payload being returned. When you publish the Zap, Segment creates a mapping in the Zapier Actions destination. 7. Your Zap now starts receiving events from Segment. If you make any changes to the mappings within Segment, these don't automatically update in Zapier, however, the events are filtered accordingly. ## Available Actions Build your own Mappings. Combine supported [triggers](/docs/segment/connections/destinations/actions/#components-of-a-destination-action) with the following Zapier-supported actions: > \[!NOTE] > > Individual destination instances support a maximum of 5 mappings. * [Send](#send-6) ### Send Send any Segment event to Zapier Send is a **Cloud** action. | Field | Description | Required | Type | | --------------------- | -------------------------------------------------------------------------------------------------------- | -------- | ------ | | Payload | The payload to send to Zapier | Yes | OBJECT | | Zapier Webhook URL | The Zapier webhook URL Segment will send data to. This URL is generated by Zapier when you create a Zap. | Yes | STRING | | Zapier Zap Identifier | The Zapier Zap identifier. This is generated by Zapier when you create a Zap. | No | STRING | | Segment FQL Query | The initial Segment FQL query for the Action mapping. This is generated by Zapier when you create a Zap. | No | STRING | ## How it works The Zapier (Actions) destination sends Segment events to Zapier, allowing you to automate workflows based on your event data. When an event matches your configured filter, Segment sends the event data to your Zap. ### Event filtering You can use either the default options that Zapier provides or write a custom query in Filter Query Language (FQL) to control which events are sent to your Zap in Zapier. Common FQL examples include: * `type = "track"` - Only send Track events. * `event = "Order Completed"` - Only send events with a specific name. In this example, Segment would only send "Order Completed" events. * `type = "track" and event = "Button Clicked"` - Combine conditions with `and`. In this example, Segment would only send Track events with a trigger type "Button Clicked". * `type != "identify"` - Exclude specific event types. In this example, Segment would send all event types except Identify events. For more information on FQL syntax and examples, see the [FQL documentation](/docs/segment/api/public-api/fql). ### Zap Identifier The Zap Identifier is a unique string that helps you identify this mapping in Segment. This is useful when you have multiple Zaps connected to the same destination and need to distinguish between them. ## Engage You can send computed traits and audiences generated using [Engage](/docs/segment/engage) to this destination as a **user property**. To learn more about Engage, schedule a [demo](https://segment.com/contact/demo). For user-property destinations, an [identify](/docs/segment/connections/spec/identify/) call is sent to the destination for each user being added and removed. The property name is the snake\_cased version of the audience name, with a true/false value to indicate membership. For example, when a user first completes an order in the last 30 days, Engage sends an Identify call with the property `order_completed_last_30days: true`. When the user no longer satisfies this condition (for example, it's been more than 30 days since their last order), Engage sets that value to `false`. When you first create an audience, Engage sends an Identify call for every user in that audience. Later audience syncs only send updates for users whose membership has changed since the last sync.