# Agent Account Order Update Flow

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

## Direct Answer

Agent Account Order Update Flow applies when a product needs status emails from an order workflow with a stable app-owned sender instead of a human OAuth mailbox or a send-only SMTP relay. Use a Nylas Agent Account as the grant, attach workspace policy and rules for guardrails, and pass the 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 status --json
nylas agent account create order-update-flow@yourapp.nylas.email --json

# Send a concrete order-status update. The metadata keys carry the
# order id, status, and order-event id so the send is idempotent and auditable.
nylas email send <agent-grant-id> \
  --to customer@example.com \
  --subject "Your order #10482 has shipped" \
  --body "Order #10482 shipped. Track it: https://yourapp.example.com/track/10482" \
  --metadata order_id=10482 \
  --metadata status=shipped \
  --metadata event_id=evt_88a1 \
  --yes \
  --json

# List reusable per-status templates (shipped, delivered, refunded):
curl -s https://api.us.nylas.com/v3/templates \
  -H "Authorization: Bearer $NYLAS_API_KEY"

# Render the chosen template before sending to verify the merged copy:
nylas email send <agent-grant-id> \
  --to customer@example.com \
  --template-id tpl_shipped \
  --template-data '{"order_id":"10482","tracking_url":"https://yourapp.example.com/track/10482"}' \
  --render-only
```

## 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 workspace policy and rules 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 production use, add dedupe keys, bounded pagination, human review for risky actions, and a stop switch that can disable sends without deleting historical records. Key each send on the order-event id so a re-delivered order webhook (delivery is at-least-once) does not email the customer twice. Subscribe to the `message.send_success`, `message.send_failed`, and `message.bounce_detected` webhook triggers so the order system learns when a "shipped" notice failed and can retry or fall back to another channel. Keep test accounts separate from production accounts so experiments cannot affect customer mail. High-volume order updates should stay under the free ceiling of 200 sends per day before moving to uncapped production.

## Minimum Data Contract

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

## 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/