Skip to content

Guide4 min read

How to log Postmark bounces in Airtable

On this page

When a receipt bounces, the customer never sees it. If a client sends transactional email through Postmark and keeps customers in Airtable, a bounce log in the base lets the team fix the address, phone the customer or stop sending to a dead inbox. Thrum's starter writes a row for each bounce within seconds of Postmark reporting it. This guide also covers Zapier and Airtable's own way of receiving data, both as their pages describe them.

Zapier

Zapier's Airtable and Postmark page (where Postmark is listed as ActiveCampaign Postmark) describes its Postmark bounce event with the line "If an email sent from Postmark bounces because of a delivery issue, you may be notified of that bounce right away by setting up a Bounce Webhook." Zapier marks it as starting a Zap instantly, and its Airtable actions include creating a record. The ready-made templates on that page run the other way, sending Postmark emails for new or updated Airtable records.

Receiving the events in Airtable itself

Airtable can take in events from another service through its "When webhook received" automation trigger (the starting event for data sent from outside). It gives you a unique address to paste into that service's settings, and later steps in the automation can create a record from what arrives. Airtable's limits are 100 KB per request and five requests a second, and each request that starts a run counts toward the run limits of the workspace's plan. Anyone with the address can start the automation, so Airtable asks you to think about where it is shared. How Postmark's bounce events would be pointed at such an address, and what they contain, is covered in Postmark's help centre, which also describes any options Postmark has of its own.

The Thrum starter

"Create a record in Airtable when an email bounces in Postmark" registers itself with the client's Postmark server when you switch it on, using the client's server token. Postmark then tells Thrum about each bounce as it happens. Switching the workflow off removes that registration again.

  1. Install the starter. Find it under Templates → Library and install it into the client whose Postmark server sends the emails. It arrives switched off with a short checklist.
  1. Connect Postmark. In Postmark, open the client's server, then API Tokens, and copy the Server API token (the key Thrum sends with). The token belongs to one server, so pick the server that sends the client's mail.

  2. Connect Airtable. Create a token at airtable.com/create/tokens with data.records:read and data.records:write, and grant it the client's base.

  3. Fill in three fields. "Postmark: Message stream" names the Postmark stream that carries these emails, which is "outbound" on a server with no others. "Airtable: Base ID" is the part of the base's address that begins with app, and "Airtable: Table" names the table that holds the log, such as Bounces.

The checklist for an example client with Postmark and Airtable connected and the stream, base ID and table filled in.
  1. Line up the columns. Every bounce writes four values. "Address that bounced" is the recipient's address. "Bounce type HardBounce" carries Postmark's name for the type of bounce, HardBounce being one of them. "What happened" carries Postmark's description of the failure, and "Address now deactivated" is true when the bounce led Postmark to deactivate the address. Airtable only accepts names that match the table's columns, so create those four columns or rename the values to the client's own.
The installed workflow on the canvas, Postmark's bounce event feeding the step that creates an Airtable record.
  1. Switch it on. From here, a bounce on that stream lands in the table within seconds.

Why one bounce makes one row

Each event Thrum receives has an identity, and if the same event arrives a second time, the copy starts nothing, so the log never doubles up. Creating the row is handled carefully too. If Airtable is busy or fails, the step is retried at waits that start at 5 seconds and double, up to 3 attempts, but if the connection breaks after the request reached Airtable, Thrum marks the run as possibly done and leaves the retry to you.

The other Postmark starters

Clicks can be logged the same way. "Create a record in Airtable when a link in an email is clicked in Postmark" records who clicked, the link, the device and whether the link was in the HTML or the text part. Clicks need tracked links on the emails, and opens are a different matter, because Thrum's own email step sends plain text, which Postmark cannot track for opens. In the other direction, an Airtable row that is new or edited can start a plain-text email from the client's Postmark server, or fill one of the client's Postmark templates with values from the run, such as a booking confirmation. Each From address has to be a confirmed sender signature or sit on a verified domain.

The Airtable and Postmark page lists every combination of the two with its starter.

Checked on 14 November 2026.

Sources

Thrum is cooking.

Get early access and you’ll be among the first in. Early members get a launch perk.