Zapier lets you connect Customer.io to hundreds of other web services. Automated connections called Zaps, set up in minutes with no coding, can automate your day-to-day tasks and build workflows between apps that otherwise wouldn’t be possible.
Each Zap has one app as the Trigger, where your information comes from and which causes one or more Actions in other apps, where your data gets sent automatically.
We currently only support Actions with the Customer.io Zapier app, we’d love to hear your use-cases for triggering Zaps from Customer.io to help us evaluate the most valuable Triggers to build.
People should have unique IDs
Each person in Customer.io is identified by a unique ID attribute. The ID value is a required field when configuring Customer.io Zap actions and most often this is the same ID that you use in your database as the primary key for your users. IDs cannot be changed later.
For more information on planning your data integration with Customer.io check out our Guide to Mapping Data in Customer.io
Once that’s done you can start creating an automation! Use a pre-made Zap or create your own with the Zap Editor. Creating a Zap requires no coding knowledge and you’ll be walked step-by-step through the setup. Need inspiration? See everything that’s possible with Customer.io and Zapier.
To help you hit the ground running, here are some popular pre-made Zaps.