Connect Customer.io to monday.com
We build integrations that move work between Customer.io and monday.com: Customer.io events create or update items on your boards, and changes on a board run actions in Customer.io.
What Customer.io can start
Events in Customer.io that can create or update items on your boards.
| Trigger |
|---|
| Customer subscribed |
| Customer unsubscribe |
| Email attempted |
| Email bounced |
| Email clicked |
| Email converted |
| Email delivered |
| Email drafted |
| Email failed |
| Email opened |
| Email sent |
| Email spammed |
| Push attempted |
| Push bounced |
| Push clicked |
| Push delivered |
| Push drafted |
| Push failed |
| Push opened |
| Push sent |
| Slack attempted |
| Slack clicked |
| Slack drafted |
| Slack failed |
| Slack sent |
| SMS attempted |
| SMS bounced |
| SMS clicked |
| SMS delivered |
| SMS drafted |
| SMS failed |
| SMS sent |
What monday.com can do in Customer.io
Actions a change on a board can run in Customer.io.
| Action |
|---|
| Campaign |
| Get campaign |
| Get many campaigns |
| Campaign: Get metrics |
| Customer |
| Create or update customer |
| Delete customer |
| Event |
| Track event |
| Event: Track anonymous |
| Segment |
| Segment: Add customer |
| Segment: Remove customer |
Recipes
When an email is opened in Customer.io, create an item in monday.com
When an item is created, track an event in Customer.io
When a status changes, create or update a customer in Customer.io
Keep Customer.io as it is. We connect it to monday.com.
We build the integration around what you already have. Customer.io keeps doing the job it does for you today, and monday.com gets the data it needs to plan and track the work around it.
Before we build, we agree which system owns each record. The integration then carries data between Customer.io and monday.com, so nobody copies it by hand.
Nothing your team relies on has to be replaced.
We highly recommend Worktables. They took the time to listen to all of our challenges and created an integrated system to manage all aspects of our operations.
What stays the same
Customer.io stays as it is
The integration connects to Customer.io the way you use it today. It moves the data, and nothing you rely on has to change.
Each record lives once
We agree which system owns each record before we build, so there is one right copy, not two.
Data arrives on its own
When data needs to reach the other side, the integration carries it. No exports, no re-keying.
How we connect Customer.io to monday.com
-
Scope
We agree which system owns each record, which events should move it, and which board it lands on.
-
Build the workflow
We build the workflow that carries data between Customer.io and monday.com and logs every run.
-
Connect the board
We map each field to your columns, groups and statuses, and test on a copy of the board before it goes live.
-
Support
We watch it after launch, fix what breaks, and change it when your process changes.
Questions about connecting Customer.io
Do we have to replace anything?
No. Customer.io stays as it is, and so does monday.com. The integration carries data between them; it does not replace either one.
What if monday.com already offers an integration with Customer.io?
Then we start from what it covers. Where it does the job, we build on it; where your process needs more, we build around it.
Can we test it before it goes live?
Yes. We test on a copy of your board before the integration touches the live one.
Who looks after it once it is running?
We do. We watch it after launch, fix what breaks, and change it when your process changes. Every run is logged, so there is a record of what moved and when.
Tell us what Customer.io and monday.com should do together
Book a free call and walk us through your process. We'll tell you what the integration should do and how we'd build it.