Marketing & email · wired today
What can agents actually do with Iterable?
Campaign and audience data drives half the questions agents get asked. The Iterable 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 Iterable tool list, exactly as agents see it
list_campaigns— List all Iterable campaigns with their state, medium and audience listslist_lists— List Iterable contact lists (id, name and list type)list_channels— List Iterable channels (the delivery channels message types belong to)list_message_types— List Iterable message types with their channel, subscription policy and rate limit
Every tool above is read-only. Write surfaces ship only after live testing, and always behind approval gates.
What the Iterable connector needs
You provide API key from your Iterable account; Quox sends it as an API key sent as a header. 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: Iterable's own API documentation ↗ covers creating and scoping the credential.
How proven is this?
This connector was blind shape-proven against the real Iterable 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.
Iterable integration FAQ
What can Quox agents do with Iterable?
Agents can run 4 read-only tools against Iterable: list campaigns, list lists, list channels, list message types. Every call is receipted in the evidence trail.
What does the Iterable integration need?
You provide API key from your Iterable account; Quox sends it as an API key sent as a header. 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 Iterable 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 Iterable connector?
This connector was blind shape-proven against the real Iterable 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.