[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.

recommended shape

scenario webhook or scheduler

HTTP or AI modules prepare the packet

dry_run=true through an HTTP module

approval checkpoint in the scenario

router branches on webhook payloads

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

An HTTP module (multipart/form-data) calls POST /api/v1/mail; a Router splits the dry run from the live send.

A Custom Webhook module receives mail events and resumes the scenario.

Store scenario_id and execution_id in metadata; a Data Store holds mail ids for reconciliation.

Use the sandbox key while the scenario is being built; switch to live only after the approval branch has been exercised.

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: <version>" \
  -H "X-Max-Cost-Cents: 1500" \
  -F "document=@scenario-packet.pdf" \
  -F "recipient_name=<recipient>" \
  -F "recipient_line1=<street>" \
  -F "recipient_city=<city>" \
  -F "recipient_state=<state>" \
  -F "recipient_zip=<zip>" \
  -F "mail_class=first_class" \
  -F "dry_run=true" \
  -F 'metadata[scenario_id]=<scenario_id>' \
  -F 'metadata[execution_id]=<execution_id>' \
  -F 'metadata[module_id]=<module_id>' \
  -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."