Postmark trigger

Overview

Receives webhook notifications from Postmark when transactional email events occur. Supports bounce, click, delivery, open, spam complaint, and subscription change events. For open events, can be configured to fire only on the first open. For bounce and spam complaint events, can optionally include the original message content in the payload. Postmark sends a POST request with a JSON body containing event-specific fields such as recipient email, message ID, bounce type, geo data, user agent info, and timestamps. Useful for monitoring email deliverability, tracking engagement, handling bounces, and managing suppression lists.

Node Type

Trigger — webhook (receives incoming HTTP callbacks)

Input / Output

Direction	Port(s)
Input	None (trigger node)
Output	Output

Credentials

This tool requires Postmark credentials. See the Credentials Guide for setup instructions.

Parameters

Parameter	Type	Required	Default	Description
Events	multiOptions	Yes	[]	Webhook events that will be enabled for this endpoint.
				Options: bounce, click (a link in the email is clicked), delivery, open, spamComplaint, subscriptionChange
First Open	boolean	No	false	Only fires on first open for event “Open”. Subsequent re-opens of the same email will not trigger. (shown when Events is open)
Include Content	boolean	No	false	Whether to include message content for events “Bounce” and “Spam Complaint”. When enabled, the original email body is included in the webhook payload. (shown when Events is bounce, spamComplaint)

Output Data

Each Postmark notification produces one output item:

• _trigger — always postmark_webhook
• _timestamp — ISO 8601 timestamp of when the request arrived
• _webhookEvent — the value of Postmark’s RecordType field, or unknown when the payload does not carry one

The Postmark payload is merged in at the top level, so the event’s own fields — RecordType, MessageID, the recipient address, bounce type and description, geo and user-agent details, and the event timestamps — sit directly on the item. Reference them downstream by expression, e.g. {{ $json.Email }}. When Include Content is enabled, bounce and spam-complaint payloads also carry the original message body.

Example Configuration

Basic open tracking:

{
  "name": "Postmark Email Opens",
  "type": "postmark_trigger",
  "parameters": {
    "events": ["open"]
  }
}

Open tracking that ignores re-opens:

{
  "name": "Postmark First Opens Only",
  "type": "postmark_trigger",
  "parameters": {
    "events": ["open"],
    "firstOpen": true
  }
}

Bounce monitoring with the original message body:

{
  "name": "Postmark Bounce Monitor",
  "type": "postmark_trigger",
  "parameters": {
    "events": ["bounce"],
    "includeContent": true
  }
}

Deliverability monitoring across bounces and spam complaints:

{
  "name": "Email Deliverability Monitor",
  "type": "postmark_trigger",
  "parameters": {
    "events": ["bounce", "spamComplaint"],
    "includeContent": true
  }
}

Engagement tracking on opens and clicks:

{
  "name": "Email Engagement Tracker",
  "type": "postmark_trigger",
  "parameters": {
    "events": ["open", "click"],
    "firstOpen": true
  }
}

Every event type on one endpoint:

{
  "name": "Complete Email Monitoring",
  "type": "postmark_trigger",
  "parameters": {
    "events": [
      "bounce",
      "click",
      "delivery",
      "open",
      "spamComplaint",
      "subscriptionChange"
    ]
  }
}

Trigger Behavior

• Activation: When the workflow is activated, a webhook endpoint is registered with the service.
• Deactivation: The webhook is automatically unregistered when the workflow is deactivated.
• Payload: The incoming webhook payload is parsed and output as workflow items.
• Verification: Supports signature verification where applicable.

Tips

This tool receives notifications from Postmark about email events like bounces, opens, and clicks. It is ideal for initiating workflows based on transactional email activity, such as tracking engagement or managing suppression lists. The tool produces a structured payload containing event-specific details like recipient email, message ID, and timestamps.