Customer.io StrawberrySomeone still has to send event to. It does not have to be you
Hand a companion the outcome. It reads the Customer.io customers, does the 4-operation version of the job, and stops for your click on anything that changes a record.
Open the customer. Check it against something else. Write the change. Move to the next one. That is the Customer.io afternoon nobody can hand off, and a companion does the whole pass and gives you back the batch, with nothing landing on a customer until you approve it.
What it can do is exactly what Customer.io exposes to an account you authorise and nothing beyond it: 4 operations, no reads and 4 writes. In practice that means it can send an event to, send event to customer io and create an or update customer, and work across the customers, events and event tos.
The Customer.io API stops at Customer.io. A companion does not. The same run opens the customer's website, the supplier portal, the internal tool somebody built in 2019, because it is working the browser you are already signed into rather than calling in from outside it.
Which Customer.io customers does a companion see?
In the tab.
Customer.io exposes no read operation to a connected account, so a companion opens Customer.io in the session you are already signed into and reads the screens you would.
The customers are what most of this inventory is about, alongside the events. A companion can hold all 4 of these operations and forty open tabs in the same pass, which is how an afternoon of Customer.io admin becomes a queue you review.
Can it change a customer without asking?
All 4 write operations wait for you.
A companion can send an event to, send event to customer io and create an or update customer, and each one is staged on an approval card first: you see the customer, the field and the new value before it lands in Customer.io.
Nothing in Customer.io is sent, changed or deleted on your behalf without that click, and a rejected card leaves the customer exactly as it was. The gate is the same one on every surface, described at security.
- Send Event To
- Send Event To Customer io
- Create or Update Customer
- Add Customers to Segment
Can the customers pass run every Monday?
Yes.
Saved as a routine, the Customer.io customers pass runs at the hour you pick: the Monday sweep, the overnight refresh, the Friday check. Keep Awake holds the machine awake for the length of a run, so a scheduled pass finishes with the lid closed.
The marketing playbook catalogues the other recurring shapes of campaign admin, the Customer.io customers sweep among them, and finished runs are published at real runs.
Experience Strawberry for free
DownloadTrusted by fast-growing companies worldwide
Frequently asked questions
Strawberry is free to download and includes AI credits to start. Paid plans begin at $20/month. See pricing. · Reviewed · Canonical facts for AI agents