Skip to main content
A marketing agent sends personal first contacts from its own dedicated address, waits for real replies, and follows up only when the answer calls for it. Because the agent has its own inbox, an out-of-office reply or a bounce changes the plan rather than disappearing into a void. The CRM API key it uses to log results lives in the vault, not in a prompt or environment variable.

What you need

An agent equipped with an inbox and a token that has the following capabilities:
  • email:read — to watch for replies, bounces, and complaints
  • email:send — to send first contacts and follow-ups
  • vault:use — to read the CRM API key without exposing it
The workspace overview shows deliveries against your plan’s recipient limits, so a campaign never runs blind.

Steps

Chat prompt example

Use this prompt in any chat client with Agent Loadout connected:
Chat prompt

TypeScript example

outreach.ts

Required permissions

Keep the same idempotency_key when retrying a send. Choose a new key only when you intend a genuinely new message. Sending follows the plan’s recipient limits and sender trust settings; the dashboard shows deliveries, bounces, and complaints per conversation.