Read bounce and delivery data from Postmark, then fix senders with approval
Connect Postmark and your team can ask about email delivery the way they'd ask a colleague. Bounce counts, delivery stats, open and click data, message stream details — all read on demand. When something needs changing, like suppressing a bad address or updating a webhook, the agent shows the plan first and asks before it writes. Luumen authenticates with an API key.
46 tools: 30 read, 16 write. Reads answer instantly. Writes require approval by default. Everything is logged.
What a governed Postmark run looks like inside Luumen.
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
This connection exposes write actions such as archive message stream, create inbound rule, create message stream, create suppressions, and more. For connected tools, admins configure which actions may run automatically and which require approval, within the access granted to the user. Review the configured approval policy before enabling write access.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to Postmark — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Connect in minutes. Every action scoped, approved, and audited from day one.