Delivery controls
Configure sender rules, forwarding, and templates.
Set the operating guardrails around who can reach the inbox, where copies go, and how repeated replies are shaped.
Token first
Make sure the agent has these scopes.
Create a new token or update the agent's current token before trying the calls below.
Required token scopes
workflows:read
workflows:write
alerts:write
Outcome
What this gives you.
The inbox can participate in an existing email stack without losing control over sender access, forwarding, or reusable copy.
Use when
The operational shape.
- An agent inbox should accept mail only from trusted senders or domains.
- Inbound copies still need to reach a human mailbox or legacy tool.
- Repeated replies should use approved templates and signatures.
API sequence
The calls to make.
01
Set sender rules
PUT/v1/sender-rules/
Allow or block inbound and outbound addresses by domain or exact sender.
Default example
Use this as the default shape for this step.
{
"inbox_id": "inb_vendor",
"inbound_mode": "allowlist",
"outbound_mode": "allowlist",
"inbound_patterns": ["@trusted-vendor.example", "finance@example.com"],
"outbound_patterns": ["@trusted-vendor.example", "finance@example.com"]
}
02
Configure forwarding
PUT/v1/forwarding/
Forward copies to humans or legacy tools while keeping the inbox record intact.
Default example
Use this as the default shape for this step.
{
"inbox_id": "inb_vendor",
"default_address": "finance@example.com",
"enabled": true
}
03
Create a reusable template
POST/v1/templates/
Use a tenant admin session to store approved wording for repeated operational replies.
Default example
Use this as the default shape for this step.
{
"name": "Vendor acknowledgement",
"subject": "Received: {subject}",
"body": "Thanks {first_name}. We received your message and will review it under {workflow_name}."
}
04
Subscribe to delivery events
POST/v1/alerts/
Notify your system when forwarding, sender, or message events need attention.
Default example
Use this as the default shape for this step.
{
"inbox_id": "inb_vendor",
"events": ["message.received", "message.sent", "message.bounced"],
"delivery": {
"type": "webhook",
"target": "https://example.com/webhooks/delivery-controls"
},
"retries": 3,
"backoff": "exponential",
"threshold": 5
}
Controls
Review points.
- Forwarding is additive; the original message remains in Gent.
- Sender rules should fail closed for sensitive workflows and stay open for intake workflows.
Related