Postmark Make integrationAutomate Postmark with Make.

Reactivates a bounced address in Postmark so it can receive your emails again. The fix happens inside Postmark, not only in your records.

Pulls one specific bounce from Postmark with its details, so your scenario can decide what to do based on facts rather than a guess.

Retrieves the bounce dump Postmark keeps for one bounce. The Make documentation does not say what it contains, so run it once and read the bundle before you rely on it.

Fetches the full details of one inbound email Postmark received. Useful when the trigger or a search gave you the message but you need everything about it in one bundle.

Looks up one email you sent through Postmark and returns its details. It answers the question a customer asks support: did you actually send it?

Returns bounce statistics for your Postmark server, the aggregate view instead of bounce by bounce. It shows whether a problem is a single address or a pattern.

Reports which browser platforms people used to open the links in your emails, based on Postmark link tracking. It tells desktop from mobile clicking habits.

Lists the browsers behind the clicks on your email links, again drawn from link tracking. Where the previous module speaks of platforms, this one names the browsers.

Shows whether clicks came from the HTML part of your emails or from the plain text version. A small detail that settles design debates quickly.

Gives the bounce statistics of a server in one call. Despite its name, the documentation describes it as a bounce overview, which makes it a quick health check.

Tells you which email clients your recipients use to open your messages, based on Postmark open tracking. Great input before redesigning a template.

Breaks down opens by platform, so you see whether your audience reads on desktop, mobile or webmail. It comes from open tracking, not from clicks.

Returns click statistics for the tracked links of your server's emails. It is the number to watch when an email's job is to send people somewhere.

Brings back the open statistics of your server, using Postmark open tracking. A simple way to see if subject lines are doing their job.

The short summary of everything a server sent: a brief overview of outbound statistics in one bundle. Start here before reaching for the detailed reports.

Counts the emails your server sent. It is the baseline every other rate is measured against, which is why it belongs in any email report.

Returns how many spam complaints your server received, the figure mailbox providers care about most. A rise here is a warning worth sharing.

Reports how many of your server's emails were tracked. It helps you read the other numbers: low opens may simply mean few emails had tracking on.

Your way out when none of the 33 modules does what you need. It calls any endpoint of the Postmark API with the connection you already set up.

Sends an email through Postmark, either written in the module or based on one of your Postmark templates. It is the module most scenarios end with.

Returns every recorded click on one email: how and when each link was clicked. As a search, it can return zero, one or several bundles.

Gives you the open history of one message, with how and when it was opened. A good fit when one important email deserves a closer look.

Retrieves the bounces of a server, filtered if you want. It is the search to use when you need the list itself, not a single case.

Pulls the inbound emails a server received. Unlike Watch Inbound Emails, it looks back at what already arrived instead of waiting for the next one.

Searches the emails your server sent and returns them as bundles. It helps when you need to act on past sends rather than new ones.