Send mail from Airtable
Move an Airtable record into a "Ready to Mail" view and paperplane’s Zapier, Make, or n8n action sends it — Certified Mail with Return Receipt for legal notices, from $12.99, address fields mapped straight from the record.
Via Zapier, Make, or n8n — no direct app yet
Instead of an Airtable automation that emails
Airtable can email a record but cannot serve a notice. A record entering a view can become Certified Mail with a Return Receipt, and the order id written back keeps the base as the audit trail.
How to set it up
- 1Keep the records to mail as rows with a status field: recipient, address fields, letter text or a linked PDF attachment, and a "Ready to Mail" view.
- 2In Zapier, Make, or n8n, trigger on a record entering that view (or a status field changing), then add the paperplane Send Letter action.
- 3Map the record’s fields into the action, setting mail_class to certified_return_receipt for legal notices that need proof of delivery.
- 4Sandbox-test the mapping, then go live — write the returned order id and status back to the record.
What the action sends for a certified notice
{
"mail_class": "certified_return_receipt",
"sandbox": true,
"text": "Dear Ms. Alvarez, ...",
"to": { "name": "Maria Alvarez", "line1": "1 Main St",
"city": "Richmond", "state": "VA", "zip": "23220" },
"from": { "name": "Alex Rivera", "line1": "12 Grove Ave",
"city": "Richmond", "state": "VA", "zip": "23221" },
"email": "alex@example.com"
}Under the hood
Airtable’s view-based status changes are a well-supported Zapier/Make/n8n trigger, paired here with the same Send Letter action every other integration uses — no paperplane-specific Airtable app exists yet. If the letter body lives in an attachment field, pull its share URL into pdf_url instead of composing text.
Supported action fields
Every integration maps into the same fixed set of fields, the ones the REST API and MCP tools take directly.
| Field | What it does |
|---|---|
| mail_class | first_class, certified, certified_return_receipt, or priority |
| text or pdf_url | the letter body as plain text, or a fetchable PDF to print as-is |
| to | recipient name + street/city/state/zip, verified against USPS data |
| from | return address, printed on the envelope and used for undeliverable mail |
| where the receipt and status updates go — no account required |
Popular Airtable workflows
Or skip the automation tool: ask Claude or ChatGPT
Every integration here sits on the same MCP endpoint agents use directly. Instead of wiring a trigger to an action, ask Claude or ChatGPT to draft and mail the letter. Same three tools (quote_letter, send_letter, get_letter_status), same price, same free sandbox.
Related integrations
Webhook (generic)
ChatGPT
Claude & MCPSend your first letter from Airtable.
Sandbox runs the whole pipeline for free and mails nothing. Live sends start at $1.99, one all-in price.
curl -X POST https://sendpaperplane.com/v1/orders \
-H 'Content-Type: application/json' \
-d '{
"mail_class": "first_class",
"sandbox": true,
"text": "Dear Ms. Alvarez, ...",
"to": { "name": "Maria Alvarez", "line1": "1 Main St",
"city": "Richmond", "state": "VA", "zip": "23220" },
"from": { "name": "Alex Rivera", "line1": "12 Grove Ave",
"city": "Richmond", "state": "VA", "zip": "23221" },
"email": "alex@example.com"
}'Common questions
Why Certified Mail with Return Receipt specifically for Airtable?
It’s the mail class legal and compliance notices typically need — proof the letter was mailed (Certified) plus electronic proof it was delivered (Return Receipt) — but any mail_class works the same way from a record.
Can a base track many recipients for the same notice?
Yes — one record per recipient, each becoming its own order with its own receipt and status; a linked view keeps the whole run auditable in one place.
What if a record’s address is incomplete?
USPS verification runs before payment on every order; a bad or incomplete address returns a structured error instead of mailing, so the automation can flag that record instead of silently failing.