[Automation integration]

Use Make scenarios to orchestrate approval-first postal mail

Use Make when the workflow needs routers, filters, and data shaping: fan records from many apps into mailbox.bot, gate approval, then branch on delivery events, forwarded documents, and inbound mail photos inside the same scenario.

Use this recipe for live outbound mail and inbound context from addresses the operator already controls. New real mailing and package addresses with street address + mailbox number: Not live yet · Launch ETA: mid/late September. Route requests to the reservation list; reservations do not assign or activate an address today.

recommended shape
source app trigger
agent or code drafts
mailbox.bot dry run
approval gate
delivery webhook
address requests reserve spot
Best for
Teams that want more branching, routing, and data shaping than a simple webhook chain.
Cross-app scenarios where CRM, forms, docs, and approvals all meet before mail is sent.
Operational flows that should react differently to mailed status, delivery proof, forwarded documents, and physical reply evidence.
Triggers
A Make webhook, scheduler, or app module detects a mail-required event.
An AI or router step decides a digital workflow now needs physical mail fallback.
A mailbox.bot webhook module resumes the scenario when mail is submitted, delivered, or failed.
[Workflow]
1

A Make scenario collects the source record, recipient, and document or generated letter body.

2

HTTP or AI modules prepare the packet and call mailbox.bot with dry_run=true.

3

An approval branch or human checkpoint confirms the live send.

4

mailbox.bot prints, mails, and emits lifecycle webhooks.

5

Make writes status, tracking, delivery proof, and any forwarded inbound artifact back to the source app or the next scenario step.

Technical pattern
Use Make HTTP modules to call POST /api/v1/mail and webhook modules to receive mailbox.bot event callbacks.
Store scenario IDs, execution IDs, and source record IDs in mailbox.bot metadata.
Use mailbox.bot MCP only when an agentic step inside the scenario should decide whether postal mail is required; otherwise keep the send deterministic through REST and branch on webhook payload contents.
Metadata to preserve
source=make
scenario_id
execution_id
module_id
source_app
source_record_id
approval_step
POST/api/v1/maildry_run=true
curl -X POST https://mailbox.bot/api/v1/mail \
  -H "Authorization: Bearer sk_agent_test_..." \
  -H "X-Mailbox-MD-Version: 3" \
  -H "X-Max-Cost-Cents: 1500" \
  -F "document=@notice.pdf" \
  -F "recipient_name=Recipient Name" \
  -F "recipient_line1=123 Main Street" \
  -F "recipient_city=San Francisco" \
  -F "recipient_state=CA" \
  -F "recipient_zip=94105" \
  -F "mail_class=certified" \
  -F "dry_run=true" \
  -F 'metadata[source]=make'
Agent prompts
"Build a Make scenario that creates a mailbox.bot dry run when this CRM record reaches Notice Required, pauses for approval, then sends the live letter."
"When mailbox.bot posts a delivered event, route the proof back through Make and update the originating record automatically."