sales-postmark

name	sales-postmark
description	Postmark platform help — transactional email delivery via REST API (`POST /email`, `POST /email/batch`), SMTP relay, Message Streams (transactional vs broadcast isolation), Handlebars Templates with layout inheritance, Inbound Email parsing, Webhooks (bounce, delivery, open, click, spam complaint, subscription change, inbound), DMARC Monitoring, Bounce Management (Rebound), Suppressions, Statistics, Bulk API, Sender Signatures, and domain authentication. Use when transactional emails aren't arriving, Postmark bounce rates are climbing, unsure how to separate transactional from broadcast streams, templates aren't rendering correctly, inbound email parsing is broken, webhooks aren't firing, or DMARC reports show authentication failures. Do NOT use for general email marketing strategy (use /sales-email-marketing), cross-platform email deliverability (use /sales-deliverability), email open/click tracking strategy (use /sales-email-tracking), or SendGrid-specific questions (use /sales-sendgrid).
argument-hint	[describe what you need help with in Postmark]
license	MIT
version	1.0.0
tags	["sales","transactional-email","deliverability","platform"]
github	https://github.com/wildbit

Postmark Platform Help

Help the user with Postmark (ActiveCampaign) platform questions — from transactional email via the REST API and SMTP relay through Message Streams, Handlebars Templates, Inbound Email, Webhooks, DMARC Monitoring, Bounce Management, Suppressions, Statistics, and integrations. Postmark is laser-focused on transactional email with best-in-class deliverability (98.7% inbox placement), originally built by Wildbit (Natalie & Chris Nagele) and acquired by ActiveCampaign in 2022.

Step 1 — Gather context

If references/learnings.md exists, read it first for accumulated knowledge.

Ask the user:

1. What area of Postmark do you need help with?

   • A) Email API — sending transactional email via REST API (POST /email, POST /email/batch), SDKs
   • B) SMTP relay — traditional SMTP integration for frameworks that don't support API
   • C) Message Streams — separating transactional and broadcast (newsletters/announcements) infrastructure
   • D) Templates — server-side Handlebars templates, layout inheritance, cross-server pushing
   • E) Inbound Email — receiving and parsing incoming emails via webhook
   • F) Webhooks — bounce, delivery, open, click, spam complaint, subscription change, inbound events
   • G) DMARC Monitoring — free weekly DMARC reports, paid detailed monitoring
   • H) Bounce Management / Suppressions — automatic bounce processing, suppression lists
   • I) Statistics — opens, clicks, delivery rates, bounce rates, spam complaints
   • J) Sender Signatures — verified sender addresses and domains
   • K) Account / Billing — plans, pricing, servers, API tokens
   • L) Something else — describe it

2. What's your role?

   • A) Developer / engineer
   • B) DevOps / infrastructure
   • C) Admin / account owner
   • D) Founder / solo operator
   • E) Agency / freelancer
   • F) Other

3. What are you trying to accomplish? (describe your specific goal or question)

If the user's request already provides most of this context, skip directly to the relevant step. Lead with your best-effort answer using reasonable assumptions (stated explicitly), then ask only the most critical 1-2 clarifying questions at the end — don't gate your response behind gathering complete context.

Note: If the user needs a specialized skill, route them there with a brief explanation of why that skill is a better fit.

Step 2 — Route or answer directly