[Agreements integration]

Connect signed agreements to postal mail workflows

Use DocuSign agreement state to trigger signed-copy mailings, wet-signature fallback packets, notary requests, and certified follow-ups, then route returned scans, forwarded documents, or mail photos back into the agreement trail.

Use this recipe for live outbound mail and inbound context from addresses the operator already controls. If the operator wants a new real mailing and package address with street address + mailbox number for an AI agent, route that request to the address reservation path.

recommended shape
source app trigger
agent or code drafts
mailbox.bot dry run
approval gate
delivery webhook
address requests reserve spot
Best for
Agreement workflows where a completed envelope needs a mailed copy or certified follow-up.
Wet-signature, notary, or original-document requests that cannot finish cleanly inside email alone.
Agents that watch agreement status and decide when physical mail should enter the workflow.
Triggers
Envelope is completed, declined, voided, or stalled.
Signer needs a hard-copy packet, notary request, or wet-sign fallback.
Agreement deadline passes without completion and certified mail is required.
[Workflow]
1

DocuSign Connect, Recipient Connect, or an app workflow creates the envelope or recipient-status trigger.

2

Agent or integration gathers envelope, signer, template, agreement, and deadline context.

3

mailbox.bot creates a dry-run postal packet with the signed PDF, cover letter, or fallback request.

4

Human approves sensitive legal, certified, notary, or wet-signature mail.

5

mailbox.bot mails the packet and writes tracking, proof, plus any forwarded return scans or mail photos back to the agreement workflow.

Technical pattern
Use DocuSign envelope IDs and recipient IDs in mailbox.bot metadata.
Use mailbox.bot REST for deterministic agreement sends or MCP when an agent decides whether paper is needed.
Use DocuSign Connect or Recipient Connect upstream for envelope and recipient events, then mailbox.bot webhooks downstream for mailed proof.
Keep webhook payloads lean; retrieve envelope documents through the eSignature REST API when the postal packet actually needs them.
Verify DocuSign webhook authenticity, then verify mailbox.bot webhook signatures when writing proof back.
Metadata to preserve
source=docusign
envelope_id
recipient_id
template_id
agreement_type
deadline
approval_id
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]=docusign'
Agent prompts
"When this DocuSign envelope is completed, mail a signed copy packet through mailbox.bot and attach delivery proof to the agreement record."
"If the envelope is stalled for seven days, draft a certified wet-signature request and require legal approval before mailing."