Resources · n8n integration

Postmark n8n integrationAutomate Postmark with n8n.

What does the Postmark n8n integration actually start? A workflow, the moment Postmark reports something about an email your app just sent. The Postmark Trigger listens to 6 events spread across 6 families and hands each one to the rest of the canvas. Made for product and ops teams already sending through Postmark.

Try the Postmark integration on n8n

Verified Trustpilot reviews · AI, automation & growth agency

Why automate

What does the Postmark n8n integration give you?

Postmark helps deliver and track application email, and reports back on what happened to each message it handled. The n8n side of that pairing is a trigger node, version 1, called Postmark Trigger. Switch a workflow on and n8n registers a webhook with Postmark, meaning a URL Postmark calls on its own, so each selected event lands on the canvas within seconds instead of waiting for a scheduled check.

Think of it as a listening post. Postmark keeps doing its job, n8n reacts to the 6 events you ticked, and everything after the trigger is ordinary workflow logic: filter, enrich, write, notify.

A support team can watch the bounce event and stop guessing. The run opens with the bounced message, appends a row to Google Sheets so the failure is logged with a timestamp, then posts the same summary to a Slack channel where someone can act on it before the customer writes in.

A sales workflow can use click instead. Someone clicked a link in the onboarding email, the trigger fires, and the record lands in Airtable next to the contact it belongs to. The follow-up task gets created while the interest is fresh rather than at the end of the week.

The third one is quieter and saves real cleanup: subscriptionChange. When Postmark reports that a recipient changed their subscription state, the workflow updates the source of truth in one pass, so the list your app reads from and the list Postmark holds stop drifting apart. Nobody has to remember to do it, which is usually the reason it stopped being done.

Postmark reaches n8n through its trigger. For anything you want to call on the Postmark API itself, the HTTP Request node hits any endpoint while reusing the same credential through predefined authentication, and it sits in the same workflow as the trigger. If you are still choosing a platform, the n8n review goes through the trade-offs, and the n8n training covers building these workflows hands on.

Connect

How do you connect Postmark to n8n?

  1. 01

    Grab the Server API Token

    Start on the Postmark side. You need a Postmark account on a Postmark server, then a Server API Token, which is the only authentication method this integration supports. It lives in the API Tokens tab under your Postmark server. Access is limited to Account Owners, Account Admins, and users who have Server Admin privileges on that server, so ask whoever holds one of those roles if the tab is not there for you.

  2. 02

    Create the credential in n8n

    Back in n8n, open the Credentials menu and create a Postmark credential, meaning the stored token n8n reuses on your behalf. Paste the Server API Token into it and save. A credential is built once and then offered in the dropdown of every node that accepts it, across all your workflows, so nobody has to copy the token around again on the next automation.

  3. 03

    Add the trigger and pick your events

    Drop the Postmark Trigger on the canvas and select the credential you just saved. Open Events and tick what this workflow should react to among the 6 available values. Two switches shape the rest: First Open and Include Content. Save, then activate the workflow so the webhook gets registered and Postmark starts calling.

Triggers

What can start a workflow from Postmark ?

Postmark Trigger is the node that starts a workflow when something happens in Postmark. It listens to 6 events, listed below by family. Pick one or several, activate the workflow: n8n registers the webhook on your Postmark account.

What you see in n8n

Every event, by family

One row per object, one chip per action. The event to tick in the node is object.action; hover a chip to read exactly when it fires.

bounce.*1
  • bounce.
    • bounce
click.*1
  • click.
    • click
delivery.*1
  • delivery.
    • delivery
open.*1
  • open.
    • open
spam.*1
    subscription.*1

      Configuration notes

      01Set Up the Postmark TriggerOne node carries this whole integration. Place the Postmark Trigger, attach the credential built from the Server API Token, and tell it what to listen for. Activation is the moment that counts: switching the workflow on is what registers the webhook URL with Postmark, and from then on each event you ticked arrives in seconds, with no polling and no interval to set.

      One node carries this whole integration. Place the Postmark Trigger, attach the credential built from the Server API Token, and tell it what to listen for. Activation is the moment that counts: switching the workflow on is what registers the webhook URL with Postmark, and from then on each event you ticked arrives in seconds, with no polling and no interval to set.

      Key parameters

      • Events: the Postmark events this node subscribes to. There are 6 of them, spread across 6 families, and each is ticked individually.
      • First Open: only fires on first open for the event Open, so a message opened again later does not start a second run.
      • Include Content: includes message content for the events Bounce and Spam Complaint, which gives the branch after the trigger something to read.
      Use cases
      one trigger can carry several events at once and a routing step downstream sends each to its own branch. Downstream nodes read a value from the event with an expression such as {{ $json.field }}, the n8n syntax for pointing at a field of the incoming item.
      02DeliveryNot every automation reacts to a problem. The delivery event, the single member of the delivery family, fires when Postmark reports that a message went out the way it was supposed to. It is the quiet path of the 6 events, and the one worth wiring when a downstream system needs to know that a message left rather than why it failed.

      Not every automation reacts to a problem. The delivery event, the single member of the delivery family, fires when Postmark reports that a message went out the way it was supposed to. It is the quiet path of the 6 events, and the one worth wiring when a downstream system needs to know that a message left rather than why it failed.

      Key parameters

      • Events: tick delivery here. Leave it unticked and this workflow simply never hears about successful sends.
      Use cases
      a billing app can flip an invoice email from pending to handled as soon as the event lands, which makes a reminder loop safe to run without sending the same notice twice. A transactional onboarding sequence can use the same event as its green light before starting the next step on a delay.
      03Bounce and Spam ComplaintThese two sit together because one switch serves both. bounce fires when a message bounces, spamComplaint when a recipient files a spam complaint, and each is its own family in the catalog. Both are the events where you usually want more than a notification, because the run has to decide what happens to that address next.

      These two sit together because one switch serves both. bounce fires when a message bounces, spamComplaint when a recipient files a spam complaint, and each is its own family in the catalog. Both are the events where you usually want more than a notification, because the run has to decide what happens to that address next.

      Key parameters

      • Events: tick bounce, spamComplaint, or both in the same trigger.
      • Include Content: includes message content for the events Bounce and Spam Complaint, so the workflow gets the message itself and not only the notice that something happened.
      Use cases
      a SaaS team routes both into one branch that flags the account, archives the content for the person who will read it later, and opens a task. Keep Include Content off when the workflow only counts and files the event, since it is the heavier of the two options.
      04Open and ClickEngagement events belong to two families of one. open fires when a recipient opens the message, click when a link inside it gets clicked. They are the pair that most often feeds a CRM or a task list, and the pair where repeat firing matters most, which is exactly what the First Open switch is there for.

      Engagement events belong to two families of one. open fires when a recipient opens the message, click when a link inside it gets clicked. They are the pair that most often feeds a CRM or a task list, and the pair where repeat firing matters most, which is exactly what the First Open switch is there for.

      Key parameters

      • Events: tick open and click together for a full engagement branch, or take just one.
      • First Open: only fires on first open for the event Open, which keeps a single recipient from restarting the same workflow every time they revisit the message.
      Use cases
      a product team can wire click to a follow-up task on the account that clicked, and leave open with First Open on to write a single first-touch line per recipient. The two events then answer different questions without fighting each other.
      05Subscription ChangeThe subscription family holds one event, subscriptionChange, and it fires when Postmark reports a change in a recipient subscription state. It is the least visible of the 6 and often the one that costs the most when it is missing, because two systems slowly stop agreeing about who should be receiving mail.

      The subscription family holds one event, subscriptionChange, and it fires when Postmark reports a change in a recipient subscription state. It is the least visible of the 6 and often the one that costs the most when it is missing, because two systems slowly stop agreeing about who should be receiving mail.

      Key parameters

      • Events: tick subscriptionChange. It works alone in a small dedicated workflow, which is usually easier to debug than folding it into a busy trigger.
      Use cases
      an ecommerce team can let the event drive the update in their own database first, then push the same change to the tools the marketing side works in. Because the event arrives within seconds, the next campaign built after the change already reflects it rather than replaying an old state.
      Need help

      Need help automating Postmark with n8n?

      A person reads every message.

      FAQ

      Postmark and n8n, the questions that come next

      01Is the Postmark n8n integration free?
      Yes, on the n8n side. The Postmark Trigger ships with n8n, so there is nothing to install and nothing extra to pay for the node itself. That holds on n8n Cloud, the hosted offer run by n8n, and on a self-hosted instance under the Community Edition and its Sustainable Use licence, installed with Docker or npm. A workflow behaves the same way in both places, so a trigger built on your laptop runs unchanged in production. What a Postmark account costs is a separate matter between you and Postmark, and this page does not cover it.
      02What credentials does the Postmark Trigger need?
      One token. Postmark supports a single authentication method here, the API token, and specifically a Server API Token taken from the API Tokens tab under your Postmark server. You need a Postmark account on a Postmark server first. The token is visible to Account Owners, Account Admins, and users who have Server Admin privileges on that server, which is worth knowing before you spend an afternoon looking for a tab your role does not show. In n8n, the token goes into a credential created once from the Credentials menu, and every later workflow picks it from a dropdown.
      03What are the limits of Postmark in n8n?
      It depends what you are asking the workflow to do. Postmark comes into n8n through its trigger: the workflow starts when a Postmark event happens, and the 6 events are chosen explicitly in the Events parameter, one tick per event you want. When you need to call an endpoint of the Postmark API from inside the same workflow, the HTTP Request node handles any endpoint and reuses the exact same credential through predefined authentication, so you are not managing a second token. That combination covers the ground: listen with the trigger, call with HTTP Request.
      04Does the Postmark Trigger react in real time?
      Yes. This trigger works by webhook, which means n8n registers a URL with Postmark when you activate the workflow, and Postmark calls that URL itself whenever one of your selected events happens. Each event arrives within seconds, with no polling involved, so there is no interval to tune and no gap between the event and the run. The practical consequence is that an inactive workflow hears nothing at all, since the registration happens at activation. Activate first, then test with a real message.
      05n8n or Make for Postmark?
      Depends on four things, and price is only one of them. Make is a hosted automation platform with no self-hosting option and billing per operation, so a busy event stream has a direct cost curve. n8n runs on its own Cloud offer or on your own infrastructure with Docker or npm, which changes who holds the data that flows through a bounce or a spam complaint. Visual logic differs too, and that is a matter of taste more than capability. Pick on hosting, data control, cost model, and how you like to build.
      Same platform

      Other docs you might need on this stack.

      Browse all integrations