Feature Marketplace · Connectors
Postmark Connector
Postmark transactional email delivery service. Syncs outbound messages, bounces, and message opens via the Postmark REST API with webhook support for delivery events.
What syncs
The Postmark records STRAX brings into your hub.
Each kind of record is mapped once to your company model in the STRAX hub, then kept current in every system that needs it. Where Postmark announces changes, they arrive as they happen.
Outbound Messages
Sent transactional messages including recipients, subject, status, and tracking settings.
Changes arrive as they happenBounces
Bounced messages including bounce type, description, and reactivation state.
Changes arrive as they happenMessage Opens
Open tracking events including email client, platform, and geographic details.
Changes arrive as they happenPostmark data in your own SQL Server, then wherever it is needed.
STRAX is a self-hosted integration platform. The Postmark records land in the STRAX hub, a SQL Server database on your own servers, where your reports, portals and workflows read them. From there the hub delivers them to the other systems you connect, whether those run on SQL Server, MySQL, PostgreSQL or another API. STRAX signs in to Postmark with an API key that you provide, stored encrypted.
How STRAX connectors work → How the STRAX integration engine works → Connecting a system, in the documentation →
About this listing
| Version | 1.0.1 |
| Author | STRAX |
| Category | Connectors |
| Published | 2026-07-15 |
What's inside
| Connector profile | 1 |
Free listing
Install it from Feature Marketplace inside STRAX
Open Feature Marketplace
In your STRAX installation, open Feature Marketplace from the navigation.
Find "Postmark Connector"
Search or browse to this listing and review the contents disclosure; every package shows what it contains before anything runs.
Install
Choose Install, or "Customise with AI" to adapt the package to your environment first. No licence is needed for free listings.
See it on your own systems.
A demo takes an hour, on your data landscape rather than ours.