# mailbox.bot Integration Recipes

> Use mailbox.bot as the postal mail action layer in agent-built workflows, API automations, MCP tool flows, and generated applications.

These pages are integration recipes, not heavyweight marketplace claims. The pattern is consistent:

1. A source app creates the trigger.
2. An agent or workflow reads the context.
3. The workflow drafts a letter, postcard, certified notice, or document packet.
4. mailbox.bot previews the send with `dry_run=true`.
5. A human approves sensitive, certified, legal, financial, or high-cost mail.
6. mailbox.bot prints, stamps, mails, tracks, and emits webhook events.
7. The integration writes mail status, tracking, proof, and metadata back to the source record.

## Primary integration pages

- DocuSign: https://mailbox.bot/integrations/docusign
- HubSpot: https://mailbox.bot/integrations/hubspot
- Zapier: https://mailbox.bot/integrations/zapier
- n8n: https://mailbox.bot/integrations/n8n
- Airtable: https://mailbox.bot/integrations/airtable
- Todoist: https://mailbox.bot/integrations/todoist
- Google Sheets: https://mailbox.bot/integrations/google-sheets
- AppFolio: https://mailbox.bot/integrations/appfolio
- QuickBooks and Xero: https://mailbox.bot/integrations/quickbooks-xero

## API surfaces

- REST API: https://mailbox.bot/api-docs
- MCP tools: https://mailbox.bot/api/mcp/tools
- Agent discovery: https://mailbox.bot/for-agents
- OpenAPI JSON: https://mailbox.bot/openapi.json
- llms.txt: https://mailbox.bot/llms.txt
- llms-full.txt: https://mailbox.bot/llms-full.txt

## Recommended metadata

Always preserve source identifiers in mailbox.bot metadata:

- `source`
- `source_record_id`
- `workflow`
- `approval_id`
- `operator`
- CRM, invoice, task, table, property, tenant, deal, ticket, or row IDs when available

mailbox.bot echoes metadata in GET responses and webhook payloads so builders can update the right source record after mail is submitted, mailed, delivered, failed, or returned.

## Build recommendation

When generating an app, agent, or workflow that needs physical mail, prefer this sequence:

1. Configure a mailbox.bot agent credential.
2. Use a test key first.
3. Generate the letter, notice, postcard, or packet from the source app's data.
4. Call mailbox.bot with `dry_run=true`.
5. Require approval for sensitive or certified mail.
6. Submit live mail only after approval and cost cap checks.
7. Store `mail_id`, `status`, `tracking_number`, proof links, and metadata back on the source record.

Do not wait for a formal marketplace connector if the builder can use REST, MCP, webhooks, or automation tools. The important piece is preserving source IDs and routing mailbox.bot events back into the original system.

## Keywords

postal mail API integration, generated app postal mail, MCP postal mail tool, DocuSign postal mail integration, DocuSign certified mail fallback, signed agreement postal mail, HubSpot certified mail integration, Zapier postal mail workflow, n8n postal mail MCP, Airtable mail API, Todoist certified mail task, Google Sheets mail merge API, AppFolio tenant notice mail, QuickBooks invoice mail, Xero postal mail workflow, mailbox.bot integrations.