Skip to content
ActionPostmarkUpdated May 2026

How do I get Postmark deliverability stats?

Short answer: Drop the "PostmarkPostmark Get Delivery Stats" action anywhere in your workflow, map the inputs from upstream nodes, and publish.

Sample request
{}
Returns
{
"Bounces": [
{
"Name": "Hard bounce",
"Type": "HardBounce",
"Count": 5
},
{
"Name": "Soft bounce",
"Type": "SoftBounce",
"Count": 3
}
],
"InactiveMails": 10
}

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for Postmark Get Delivery Stats.

Any of these apps can fire this action as part of a workflow.

FAQ

Questions about Postmark Get Delivery Stats.

What does the Postmark Get Delivery Stats action do in Postmark?
Returns deliverability metrics — sent, delivered, bounced, opened, clicked, complained — over a date range. For "is our deliverability healthy?" monitoring workflows.
What inputs does Postmark Get Delivery Stats require?
Postmark Get Delivery Stats has no required inputs. Sensible defaults are applied if you leave fields blank.
Can I use dynamic inputs from earlier workflow nodes?
Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.
What happens if Postmark returns an error?
The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.
Does Postmark Get Delivery Stats support batch operations?
Yes. Run Postmark Get Delivery Stats inside a Loop node to process arrays. Tiny Command handles Postmark's rate limits automatically so you don't have to throttle manually.
More actions

Other Postmark actions.

Send postmark get delivery stats from your workflows.

Triggered by anything in the catalog. Free tier available. No credit card.