01 · Direct answer
How do you send a postcard from an Airtable record?
Use the Airtable record ID as the source key. Require separate recipient and postal fields. Store the template version, eligibility result, and mail result in dedicated fields. Move failed records to a visible exception view instead of retrying every edit.
A record-created trigger can fire before a person finishes entering the address.
- Create the stateUse Draft, Ready to mail, Held, and Sent or Released values.
- TriggerRun when the record enters Ready to mail.
- Write backSave mailpiece ID, result, time, and exception reason.
02 · Direct answer
How do you send direct mail from a Make scenario?
Normalize the source data before the mail action. Build the idempotency key from the source record and event. Use Make's error-handling route to record failures. Test the request with live mail disabled.
Do not let automatic retries create a new key. The same event must keep the same key.
03 · Direct answer
How do you send direct mail from an n8n workflow?
Persist the source event ID before the outbound request. Route invalid addresses and duplicate events to separate branches. Store the returned result before later status-event handling.
Self-hosted and cloud n8n setups can differ. Confirm credentials, network access, and retry behavior in the running environment.
04 · Direct answer
How do you send a welcome card when a new QuickBooks customer is created?
Map the QuickBooks customer ID, customer name, billing or shipping postal fields, and template ID. Confirm the intended address. Filter out test, vendor, duplicate, and incomplete customer records. Record the result without changing fields that replay the trigger.
A new QuickBooks customer is not proof that an invoice was paid.
05 · Direct answer
How do you send a card after a successful Stripe payment?
Verify the webhook signature. Use the Stripe event ID for idempotency and the payment object ID as the source record. Resolve a complete mailing address from the permitted object or business system. Handle duplicate events and asynchronous payment states before release.
Stripe can deliver webhook events more than once and does not guarantee event order. Store processed event IDs.
- Select successUse the payment event that matches the integration's payment method and fulfillment rule.
- VerifyCheck the signature and retrieve the event when required.
- Resolve addressDo not assume every successful payment includes a usable postal address.
- DeduplicateReuse the Stripe event ID and keep it after processing.
Implementation worksheet
Tool-to-mail event matrix
Use the stable identifier from the source tool. Do not create identity from a name or address alone.
| Tool | Recommended source key | Important boundary |
|---|---|---|
| Airtable | Record ID plus Ready-to-mail transition | Record creation can occur before data entry is complete. |
| Make | Upstream record or event ID | Retries must reuse the same idempotency key. |
| n8n | Upstream record or event ID | Confirm instance credentials, network access, and retry settings. |
| QuickBooks | Customer ID | Customer creation does not prove invoice payment. |
| Stripe | Event ID plus payment object ID | Verify signatures, duplicates, event order, and address presence. |
Preflight checklist
- Use one stable source-event ID and save it with the mail record.
- Require recipient name, address line 1, city, state, and ZIP Code before release.
- Set a duplicate rule for the person, household, property, order, or job.
- Render a proof with a test record before any funded send.
- Define who can pause the workflow and who can approve release.
- Store the source record ID, campaign ID, and returned mailpiece ID together.
- Treat mailstream events as operational signals, not proof of attention or revenue.
FAQ
Questions to resolve before launch
Can a new QuickBooks customer trigger a payment thank-you card?
No. Customer creation does not prove payment. Use and verify a payment event for payment-specific copy.
Can Stripe send the same webhook more than once?
Yes. Stripe documents duplicate delivery. Store processed event IDs and enforce idempotency.
Does a successful payment always contain a mailing address?
No. Resolve and validate the postal address before the record can release.
Are these native Sendvo integrations?
No native connectors are claimed. Confirm the supported connection for each account.
Primary sources
Sources and review notes
- Airtable: Automation trigger referenceOfficial trigger behavior and record-state options.
- Make: HTTP appOfficial HTTP module guidance.
- n8n: HTTP Request nodeOfficial HTTP Request configuration.
- Intuit: QuickBooks Online webhooksOfficial event-notification behavior.
- Stripe: WebhooksOfficial signatures, retries, ordering, and duplicate-event guidance.
- Stripe: PaymentIntent eventsOfficial successful-payment status guidance.
Product plans, trigger names, and connector access can change. Check the linked documentation and your account before production use. Sendvo last reviewed these sources on August 31, 2026.