Untaggle HelpSign in →

Connect Postmark

If HighLevel sends your marketing email through Postmark (a broadcast stream over custom SMTP), the unsubscribe button and footer link in those emails are Postmark's — and HighLevel never hears about the people who use them. Connect Postmark and, from that moment on, Untaggle picks up those unsubscribes and sets their email DND in HighLevel, plus an unsubscribe on your other email platforms.

What you need

  • A Server API token — in Postmark, open the server that sends your broadcasts, then API Tokens. Any Server token works. The Account API token does not, and Untaggle will tell you if you paste that one.
  • At least one broadcast message stream on that server. Unsubscribe sync covers broadcast streams only — transactional mail is never read.
  • You must be an admin of your Untaggle account.

Steps

  1. In Untaggle, open Connections and click + Connect platform, then pick Postmark.
  2. Paste the Server API token and click Test connection — you'll see a ✓ with your server's name.
  3. Click Connect. That's it — Untaggle registers a “Subscription change” webhook on each broadcast stream the server has at that moment. Webhooks you already have there are left untouched. Add a broadcast stream later? Re-enter the token under the connection's Credentials tab and the new stream gets its webhook too.

What this enables

  • Unsubscribe sync, one way out of Postmark: when a recipient unsubscribes (the one-click button in Gmail or the link in Postmark's footer), reports an email as spam, or hard-bounces, Untaggle sets their email DND in HighLevel and unsubscribes them on your other email platforms — wired for you on connect. Unsubscribes from before you connected stay in Postmark's suppression list and are not picked up. How unsubscribe sync works.
  • Nothing flows back. Postmark has no contacts to tag or opt out, so opt-outs from your other platforms are not written to it, and taking an address off Postmark's suppression list never clears a DND or re-subscribes anyone.

Why HighLevel needs this

In our testing (October 2026), HighLevel sent no unsubscribe header of its own over custom SMTP and blanked Postmark's in-body unsubscribe placeholder, so Postmark's managed unsubscribe (the header and the footer link) was the only one-click unsubscribe those emails carried. Those opt-outs land on Postmark's suppression list, where Postmark stops delivering — but HighLevel would keep the contact subscribed and keep handing Postmark mail for them. The HighLevel-side unsubscribe link, if you also include one in the body, already sets DND by itself and needs nothing from Untaggle.