Marketing & email · wired today
What can agents actually do with Customer.io?
Campaign and audience data drives half the questions agents get asked. The Customer.io connector is one of 205 executable connectors and gives agents 4 read-only tools, with the credential held in the vault and every call receipted.
The Customer.io tool list, exactly as agents see it
list_campaigns— List Customer.io automations (campaigns) in the workspace, with their trigger type and statelist_newsletters— List Customer.io newsletters (one-time sends), most recent first when sorted desclist_segments— List Customer.io segments with their type, state and descriptionget_customer_activities— List recent Customer.io activities for one person (message sends, attribute changes, events) from the last 30 days
Every tool above is read-only. Write surfaces ship only after live testing, and always behind approval gates.
What the Customer.io connector needs
You provide API key, site ID from your Customer.io account; Quox sends it as a bearer token. The credential is stored encrypted in the vault and resolved just-in-time, so agents use it without ever seeing it.
Where to get it: Customer.io's own API documentation ↗ covers creating and scoping the credential.
How proven is this?
This connector was blind shape-proven against the real Customer.io API: every endpoint it declares answered measurably differently from a deliberately bogus control request, without any account or credential involved. It is Beta: proven against the live API surface, not yet run with a real credential.
Customer.io integration FAQ
What can Quox agents do with Customer.io?
Agents can run 4 read-only tools against Customer.io: list campaigns, list newsletters, list segments, get customer activities. Every call is receipted in the evidence trail.
What does the Customer.io integration need?
You provide API key, site ID from your Customer.io account; Quox sends it as a bearer token. The credential is stored encrypted in the vault and resolved just-in-time, so agents use it without ever seeing it.
Do agents see my Customer.io credentials?
No. Credentials live encrypted in the Quox vault and are resolved server-side at call time. Agents invoke tools; they never receive the underlying secret.
How proven is the Customer.io connector?
This connector was blind shape-proven against the real Customer.io API: every endpoint it declares answered measurably differently from a deliberately bogus control request, without any account or credential involved. It is Beta: proven against the live API surface, not yet run with a real credential.