[Tasks integration]

Turn Todoist tasks into postal mail follow-ups

Use Todoist as a lightweight operator queue where tasks, labels, comments, or due dates become mailbox.bot postal mail drafts and proof-backed follow-ups.

recommended shape
source app trigger
agent or code drafts
mailbox.bot dry run
approval gate
delivery webhook
Best for
Founder/operator workflows that start as tasks rather than CRM records.
Manual approval queues for agents preparing mail.
Deadline follow-ups where a task should produce a mailed notice.
Triggers
Task label changes to mail-required.
Task due date arrives and the digital follow-up failed.
Task comment contains recipient and document context.
[Workflow]
1

Agent or automation reads the Todoist task and comments.

2

mailbox.bot dry run creates a postal mail draft.

3

Human approves by label, comment, or external approval UI.

4

mailbox.bot sends and tracks the mail.

5

Automation comments back with mail status and proof.

Technical pattern
Use Todoist task IDs and project IDs in metadata.
Use REST for direct sends from workflow code or MCP when an agent is deciding what to mail.
Write mailbox.bot events back as task comments or labels.
Metadata to preserve
source=todoist
project_id
task_id
section_id
label
operator
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]=todoist'
Agent prompts
"When a Todoist task has the label mail-required, draft a mailbox.bot letter and add the dry-run estimate as a comment."
"Build a Todoist approval queue where approved tasks send certified mail through mailbox.bot."