Postmark
Send the right update through Postmark at the right moment, with a person approving what reaches customers.
29 ways to read, 7 ways to write, each write switched on by you.
Quality checks
Built and tested with example responses.
- Ready to connect: doneEvery listed action is built in.
- Built and tested with example responses: doneEach action is built from the provider’s published API and tested against example responses, errors, rate limits and paging.
Connected, approved, proven.
The things teams do most with Postmark, an example flow with a person in the loop, and what Nexra keeps as proof.
Top actions
- Send emailApproval by rule
- Create message streamApproval by rule
- Get bounce counts by dayRead
Example flow
- Postmark · Get bounce counts by dayDone
- Postmark · Send emailNeeds approval
- Nexra · Record the decision and result in the evidence chainProven
Example workflow. Routine runs go through on their own. Only a change your rules flag, such as one over a limit you set, waits for the right person, who sees the exact change and the rule before it reaches Postmark.
What gets logged
- Whether it ran on its own or who approved it, and under which rule
- A fingerprint of the exact request sent to Postmark
- Postmark's reply: what it created or changed
- One entry in the evidence chain, linked to the one before
Try this in the sandbox
Run the whole flow with test data in your sandbox, then connect a ActiveCampaign (Postmark) test account before you go live.
For developers
Technical detail
Send transactional and templated email with Postmark, manage templates and message streams, and read outbound and inbound activity, bounces, suppressions, stats, domains and webhooks.
ActiveCampaign (Postmark) API docs- Source actions
- 29
- Destination actions
- 7
- Data types
- 22
What you can map
Reads are always available. Writes are off until you switch them on for a connection, and governed writes follow your policies.
Bounce stats1
- Get bounce counts by daySource
Hard bounces, soft bounces, SMTP API errors and transient bounces per day.
Bounces3
- Get bounceSource
One bounce with its type, details and reactivation status.
- List bouncesSourceIncremental
Bounces and spam complaints filtered by type, address, tag, stream or date.
- Reactivate bounced addressDestinationProvider duplicate protectionApproval before production
Reactivates the address deactivated by a bounce so Postmark delivers to it again. Only works where the bounce reports CanActivate.
Click stats1
- Get clicks by daySource
Total and unique link clicks per day for a period, tag or stream.
Clicks1
- List message clicksSource
Link click events for outbound messages, filtered by recipient, tag or stream.
Delivery stats1
- Get delivery statisticsSource
Bounce counts by bounce type and the number of inactive addresses.
Domains2
- Get domainSource
One sending domain with its DKIM and Return-Path DNS records.
- List domainsSource
Sending domains with DKIM and Return-Path verification status.
Email1
- Send emailDestinationNot retried automaticallyApproval before production
Sends one transactional email (up to 50 recipients) through a transactional message stream.
Inbound messages2
- Get inbound message detailsSource
One inbound message with bodies, headers and attachment metadata.
- Search inbound messagesSourceIncremental
Inbound messages processed by the server, filtered by recipient, sender, subject, mailbox hash, status or date.
Message streams4
- Create message streamDestinationProvider duplicate protectionApproval before production
Creates a transactional or broadcast message stream. Creating a stream sends nothing.
- Get message streamSource
One message stream with its unsubscribe handling.
- List message streamsSource
Transactional, broadcast and inbound message streams on the server.
- Update message streamDestinationProvider duplicate protectionApproval before production
Updates a stream's name, description or unsubscribe handling.
Open stats1
- Get opens by daySource
Total and unique opens per day for a period, tag or stream.
Opens1
- List message opensSource
Open events for outbound messages, filtered by recipient, tag or stream.
Outbound messages2
- Get outbound message detailsSource
One sent message with bodies and its delivery, open, click and bounce events.
- Search outbound messagesSourceIncremental
Sent messages filtered by recipient, sender, tag, status, stream or date, newest first.
Outbound stats1
- Get outbound statisticsSource
Sent, bounced, spam complaint, open and click totals for a period, tag or stream.
Send stats1
- Get sent counts by daySource
Messages sent per day for a period, tag or stream.
Sender signatures2
- Get sender signatureSource
One sender signature with its DKIM and Return-Path details.
- List sender signaturesSource
Sender signatures with their confirmation status.
Server1
- Get serverSource
The server this token belongs to, with its tracking and delivery settings.
Servers2
- Get server by IDSource
One server on the account (needs the Account API token).
- List serversSource
Servers on the Postmark account (needs the Account API token).
Spam stats1
- Get spam complaints by daySource
Spam complaints per day for a period, tag or stream.
Suppressions1
- List suppressionsSource
Addresses suppressed on one message stream because of hard bounces, spam complaints or unsubscribes.
Template email1
- Send email with templateDestinationNot retried automaticallyApproval before production
Sends one transactional email rendered from a Postmark template and a template model.
Templates4
- Create templateDestinationNot retried automaticallyApproval before production
Creates a standard template or layout.
- Get templateSource
One template with its subject and bodies.
- List templatesSource
Templates and layouts on the server.
- Update templateDestinationProvider duplicate protectionApproval before production
Updates a template's name, alias, subject, bodies or layout.
Webhooks2
- Get webhookSource
One webhook with its URL, stream and enabled triggers.
- List webhooksSource
Webhooks configured on the server, optionally for one message stream.
Access and limits
- Authentication
- Server API token
- Plans and access
- All Postmark plans, including the free developer tier (100 emails per month). Sending needs a confirmed sender signature or verified domain. Server API tokens are scoped to one Postmark server. Account-level reads (servers, domains, sender signatures) need the optional Account API token, which only account owners and admins can see.
- Test environment
- Create a server in Sandbox mode, or use the POSTMARK_API_TEST token, to accept messages without delivering them.
- Rate limits
- Postmark does not publish a fixed request rate; it returns HTTP 429 when a server sends too quickly. Messages are limited to 50 recipients and 10 MB.
- Pagination
- count/offset on messages, bounces, opens, clicks and templates (count up to 500; offset + count up to 10,000 for message searches).
- Provider events
- Per-stream webhooks for delivery, bounce, spam complaint, open, click and subscription change events. Flows run on demand, on a schedule, or when a scheduled check finds new or changed records.
Before you build a flow
- Only transactional (outbound) message streams can be used to send; broadcast streams are refused to avoid audience-wide sends.
- Intentionally excluded: batch and bulk sends (/email/batch, /email/batchWithTemplates, bulk broadcast API), suppression creation and deletion, stream archiving, template, domain, sender, server and webhook writes other than those listed, and all deletes.
- Bounce reactivation only succeeds where Postmark reports CanActivate; reactivating a hard bounce can hurt sender reputation if the address is still invalid.
- Raw bounce dumps and inbound message bodies beyond the details read are not exposed, to limit personal data.
- Server list and get never return the server's API tokens; webhook reads never return basic-auth passwords or custom header values.
- Account-level reads (servers, domains, sender signatures) fail with a configuration error until an Account API token is added.
- Postmark has no idempotency key for sends; uncertain sends are not repeated automatically.
- Message search is limited by Postmark to the most recent 10,000 results (offset + count) and the server's retention window (45 days by default).
- Suppressions are read per message stream and are not paginated by Postmark.
- Postmark answers most validation failures with HTTP 422 and an ErrorCode; Nexra reports them as validation errors.
Developer reference
- Create the ActiveCampaign (Postmark) credentials described above with the narrowest permissions your flows need.
- In Nexra, open Connect, then Connections, then New connection, choose Postmark, enter its settings and credentials, and tick only the write actions you need. Connection guide
- Test the connection, then use its actions as flow sources and destinations. Flow guide
Machine-readable detail: GET /api/public/connect/connectors/postmark and the Connections API.