Customer.io × AmbactiBring Customer.io into
the flow of work.
A little less busywork with Customer.io.
Gather contextDo the workReview & share
Campaign3 capabilities+
- Get many campaignsRead
- Get metrics for a campaignRead
- Get a campaignRead
Customer2 capabilities+
- Create or update a customerWrite
Create a new customer, or update the current one if it already exists (upsert)
- Delete a customerWrite
Event2 capabilities+
- Track an anonymous eventWrite
- Track a customer eventWrite
Segment2 capabilities+
- Add a customer to a segmentWrite
- Remove a customer from a segmentWrite
Update events32 capabilities+
- Customer SubscribedEvent
- Customer UnsubscribeEvent
- Email AttemptedEvent
- Email BouncedEvent
- Email ClickedEvent
- Email ConvertedEvent
- Email DeliveredEvent
- Email DraftedEvent
- Email FailedEvent
- Email OpenedEvent
- Email SentEvent
- Email SpammedEvent
- Push AttemptedEvent
- Push BouncedEvent
- Push ClickedEvent
- Push DeliveredEvent
- Push DraftedEvent
- Push FailedEvent
- Push OpenedEvent
- Push SentEvent
- SMS AttemptedEvent
- SMS BouncedEvent
- SMS ClickedEvent
- SMS DeliveredEvent
- SMS DraftedEvent
- SMS FailedEvent
- SMS SentEvent
- Slack AttemptedEvent
- Slack ClickedEvent
- Slack DraftedEvent
- Slack FailedEvent
- Slack SentEvent
Frequently asked
questions.
What could an Ambacti integration do with Customer.io?
The documented operations include Campaign: Get many campaigns; Campaign: Get metrics for a campaign; Campaign: Get a campaign; Customer: Create or update a customer.
Could I keep a workflow read-only?
For a read-only workflow, limit account permissions to reading data and exclude actions that create, update, or delete records.
Will every action run automatically?
Choose which steps could run on their own and which should pause for review. Changes should follow the permissions and approval rules you set.
Do I need to review actions in Customer.io?
Decide which work could run on its own and which steps need your review.