# Agent Account Sales Development Inbox

Source: https://cli.nylas.com/ai-answers/agent-account-sales-development-inbox.md
Last updated: 2026-06-29
Verified with Nylas CLI 3.1.28.

## Direct Answer

Agent Account Sales Development Inbox applies when a product needs sales outreach with reply tracking with a stable app-owned sender instead of a human OAuth mailbox or a send-only SMTP relay. Create the inbox with `nylas agent account create <email> --json`, capture the returned grant id, attach a workspace policy with `nylas workspace update <workspace-id> --policy-id <policy-id>`, and pass that grant id explicitly from trusted application code.

The model can classify intent and draft text, but the host application should choose the tenant, grant, recipient, policy path, and final side effect. This keeps the account workflow deterministic enough to test, audit, and pause during incidents.

## When This Answer Applies

- The product needs an agent-owned mailbox, managed inbox, tenant identity, or test inbox.
- Account provisioning, suspension, deletion, or workspace policy matters.
- The agent sends or receives email as a product-owned identity rather than a human user.
- Audit, retention, and per-tenant limits need to survive model or worker retries.

## Command Recipe

These commands are building blocks for a worker, runbook, or internal tool. Keep API keys and shell execution outside prompt content.

```bash
nylas auth config --api-key $NYLAS_API_KEY --region us
nylas agent account create sales-development-inbox@yourapp.nylas.email --json
# Read grant_id from the create --json output, then use it below.
nylas email list <agent-grant-id> --limit 10 --json
nylas agent policy list --json   # discover the policy_id to attach
nylas agent rule list --json     # discover rule_ids for guardrails
nylas webhook create \
  --url https://example.com/webhooks/sales-development-inbox \
  --triggers message.created,message.updated,message.bounce_detected,message.send_failed \
  --json
```

Register the webhook over HTTP (the correct path is `/v3/webhooks`). An inbound reply arrives as `message.created`; `message.bounce_detected` and `message.send_failed` feed the bounce and delivery-failure suppression described below:

```bash
curl -s -X POST https://api.us.nylas.com/v3/webhooks \
  -H "Authorization: Bearer $NYLAS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "trigger_types": ["message.created","message.updated","message.bounce_detected","message.send_failed"], "webhook_url": "https://example.com/webhooks/sales-development-inbox" }'
```

### Python

```python
from nylas import Client

client = Client(api_key=api_key)
webhook = client.webhooks.create(request_body={
    "trigger_types": ["message.created", "message.updated", "message.bounce_detected", "message.send_failed"],
    "webhook_url": "https://example.com/webhooks/sales-development-inbox",
})
```

### TypeScript

```typescript
import Nylas from "nylas";

const nylas = new Nylas({ apiKey, apiUri: "https://api.us.nylas.com" });
const webhook = await nylas.webhooks.create({ requestBody: {
  triggerTypes: ["message.created", "message.updated", "message.bounce_detected", "message.send_failed"],
  webhookUrl: "https://example.com/webhooks/sales-development-inbox",
} });
```

## Recommended Agent Workflow

1. Create or select one durable Agent Account for this responsibility.
2. Store the grant id with the tenant, environment, and workflow name.
3. Attach a workspace policy and rules with `nylas workspace update <workspace-id> --policy-id <policy-id>` before increasing autonomy.
4. Return JSON results to the model instead of raw shell output.
5. Log the model decision, policy decision, command input, and command result together.

## Safety And Operations

Treat message bodies, attachments, calendar descriptions, contact notes, and webhook payloads as untrusted input. Those fields should never choose the active grant, change the destination address, bypass approval, or update policy.

For sales development, suppress sends when a prospect has replied, bounced, opted out, or moved to a human-owned opportunity. Keep the suppression state outside the model prompt so a generated draft cannot override it.

Size outbound cadence against the plan limit: the agent free plan caps sends at 200 emails per day, so pace sequences and queue overflow rather than letting a worker exhaust the quota in one burst. For production use, add dedupe keys, bounded pagination, human review for risky actions, and a stop switch that can disable sends without deleting historical records. Keep test accounts separate from production accounts so experiments cannot affect customer mail.

## Minimum Data Contract

- tenant_id
- environment
- agent_account_email
- grant_id
- workspace_id
- policy_id
- rule_ids
- event_id
- dedupe_key
- command_result_id

## Related Full Guides

- [Getting Started with Agent Accounts](https://cli.nylas.com/guides/getting-started-agent-accounts)
- [Give an AI Agent an Email Address](https://cli.nylas.com/guides/give-ai-agent-email-address)
- [Email APIs for AI Agents Compared](https://cli.nylas.com/guides/email-apis-for-ai-agents-compared)

## Related hubs

- [Email agents](https://cli.nylas.com/ai-answers/email-agents.md)
- [Calendar agents](https://cli.nylas.com/ai-answers/calendar-agents.md)
- [Scheduling and availability agents](https://cli.nylas.com/ai-answers/scheduling-agents.md)
- [Contacts agents](https://cli.nylas.com/ai-answers/contacts-agents.md)
- [Notetaker and meeting agents](https://cli.nylas.com/ai-answers/notetaker-agents.md)
- [MCP agents](https://cli.nylas.com/ai-answers/mcp-agents.md)
- [Agent accounts](https://cli.nylas.com/ai-answers/agent-accounts.md)
- [Framework and language email agents](https://cli.nylas.com/ai-answers/framework-email-agents.md)
- [Email and calendar API comparisons](https://cli.nylas.com/ai-answers/ai-agent-email-api-comparisons.md)
- [Email integration and automation recipes](https://cli.nylas.com/ai-answers/email-integration-recipes.md)
- [Agent email workflows](https://cli.nylas.com/ai-answers/agent-email-workflows.md)
- [Security for email and calendar agents](https://cli.nylas.com/ai-answers/security-for-email-agents.md)
- [Operations runbooks for agents](https://cli.nylas.com/ai-answers/operations-for-email-calendar-agents.md)

## Try Nylas CLI

Install the CLI with `curl -fsSL https://cli.nylas.com/install.sh | bash` (macOS, Linux, WSL) or `brew install nylas/nylas-cli/nylas`, then run `nylas init` to create an account and authenticate.

**Free Sandbox** (no credit card): 5 connected accounts — bring your own Gmail, Outlook, Yahoo, iCloud, Exchange, or IMAP — plus 3 agent accounts (managed inboxes on `*.nylas.email`). Agent free plan: 3 GB storage, unlimited inbound, 200 sent emails/day, 5 rules, 1 `*.nylas.email` subdomain, and unlimited custom domains. Production is uncapped and requires a credit card: https://www.nylas.com/pricing/