Marketing & email · wired today
What can agents actually do with Resend?
Campaign and audience data drives half the questions agents get asked. The Resend 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 Resend tool list, exactly as agents see it
list_domains— List the sending domains registered on the Resend account, with verification status and regionlist_api_keys— List the Resend API keys on the account (metadata only, the secret token is never returned)list_audiences— List the Resend audiences (contact lists) on the accountget_email— Get one sent Resend email by ID, including recipients, subject and its latest delivery event
Every tool above is read-only. Write surfaces ship only after live testing, and always behind approval gates.
What the Resend connector needs
You provide API key from your Resend 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: Resend's own API documentation ↗ covers creating and scoping the credential.
How proven is this?
Resend answers every unauthenticated request identically, so its endpoint paths rest on Resend's own published API reference (cited in the connector spec). The credential wire format was verified against the real host. Like every factory connector, it is Beta: it has not yet been run with a real credential.
Resend integration FAQ
What can Quox agents do with Resend?
Agents can run 4 read-only tools against Resend: list domains, list api keys, list audiences, get email. Every call is receipted in the evidence trail.
What does the Resend integration need?
You provide API key from your Resend 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 Resend 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 Resend connector?
Resend answers every unauthenticated request identically, so its endpoint paths rest on Resend's own published API reference (cited in the connector spec). The credential wire format was verified against the real host. Like every factory connector, it is Beta: it has not yet been run with a real credential.