Postmark integration

What it does

The Postmark integration lets your agency send transactional email from any workflow and turn delivery feedback into automation. Connect a client's Postmark server token once and your workflows can send single emails, send batched runs of up to 500 messages per call, render templated messages from the client's library, look up historical message details, pull aggregate engagement stats, and react in real time when Postmark reports a delivery, bounce, or open.

Connect a Postmark account

1. Open your workspace in TaskJuice and navigate to Connections.
2. Choose Postmark and click Connect.
3. In a new tab, sign in to account.postmarkapp.com as the client and open the server you want to integrate.
4. Open the API Tokens tab on that server and copy the server token (one server per client keeps revocation scoped).
5. Paste the token into TaskJuice and save the connection.

To rotate or revoke the token later, return to the server's API Tokens tab in Postmark, regenerate the token, and update the TaskJuice connection.

Triggers

• postmark/email-delivered fires when Postmark confirms a recipient mail server accepted an outbound message (Delivery webhook event).
• postmark/email-bounced fires when an outbound message hard- or soft-bounces, with the bounce type, description, and whether the recipient can be reactivated (Bounce webhook event).
• postmark/email-opened fires when a tracked recipient opens a message, with the platform, user agent, client, and approximate geo from Postmark's open-tracking pixel (Open webhook event).

Each webhook delivers one event per POST. Configure the webhook in the Postmark UI with a custom Authorization header value matching the shared secret you supply when subscribing the trigger; TaskJuice verifies the header on every inbound POST and rejects unsigned traffic.

Actions

• postmark/send-email sends a single transactional email with HTML and plain-text bodies, optional tag, message stream, reply-to, and open/link tracking flags.
• postmark/send-email-batch sends up to 500 messages in a single request, returning a per-recipient success or error code for each.
• postmark/send-email-with-template renders a templated email by template id or alias, interpolating a template-model object into the saved template before sending.
• postmark/list-outbound-messages pages through the outbound message history with filters for recipient, sender, tag, status, and date range.
• postmark/get-outbound-message-details fetches the full delivery and engagement timeline for one outbound message by id.
• postmark/get-outbound-stats returns aggregate counts and rates for sends, bounces, spam complaints, opens, and unique opens across a filterable date range.

Known limitations

• The integration calls the Postmark REST API with the connected server token. Per-token send rates, sandbox restrictions, and verified-sender requirements are governed by the client's Postmark account, not by TaskJuice. When Postmark returns a 422 with a validation error code, TaskJuice surfaces it as a non-retryable validation failure; 429 responses are surfaced as retryable rate limits.
• A server token scopes to one Postmark server. Connect each client server separately so revocation, sender signatures, and message streams stay isolated.
• Postmark does not sign webhook payloads with HMAC. Inbound authentication relies on a static shared secret carried in the Authorization header. Treat the secret like an API key, store it in TaskJuice, and rotate it in Postmark when staff rotate.
• Open and click tracking is governed by the per-message TrackOpens and TrackLinks flags and by the server's defaults. Workflows that branch on the Open trigger must confirm tracking is enabled on the originating send.