Postmark MCP integration for AI agents.
Connect AI agents to Postmark through 12 structured actions, including get bounces, create template, and validate template. Review authentication, inputs, wo…
- ACTION CONTRACTS
- 12
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Postmark integration exposes
The Postmark Agent App exposes 12 provider-backed actions for communication and marketing work. Its current contract lets an authorized agent get postmark bounces for the current server with optional filters, create a postmark template, and validate postmark template content and render test output. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Postmark account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Postmark capabilities.
Showing 12 of 12 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_bouncesREADGet Postmark bounces for the current server with optional filters.
INPUTS: count / offset / type / inactive / emailFilter
create_templateWRITECreate a Postmark template.
INPUTS: Name / Subject / HtmlBody / TextBody / TemplateType
validate_templateREVIEWValidate Postmark template content and render test output.
INPUTS: Subject / HtmlBody / TextBody / TestRenderModel / InlineCssForHtmlTestRender
edit_templateWRITEEdit an existing Postmark template.
INPUTS: templateIdOrAlias / Name / Subject / HtmlBody / TextBody
get_outbound_message_detailsREADGet detailed content and events for one outbound Postmark message.
INPUTS: messageId
get_serverREADGet the current Postmark server configuration for the connected server token.
get_templateREADGet one Postmark template by template ID or alias.
INPUTS: templateIdOrAlias
list_templatesREADList Postmark templates for the current server.
INPUTS: count / offset / TemplateType / LayoutTemplate
search_outbound_messagesREADSearch outbound Postmark messages with filters and pagination.
INPUTS: count / offset / recipient / fromemail / tag
send_batch_with_templatesWRITESend up to 500 templated emails in a single Postmark batch request.
INPUTS: Messages
send_emailWRITESend a transactional email through the current Postmark server.
INPUTS: From / To / Cc / Bcc / Tag
send_email_with_templateWRITESend a single templated email through the current Postmark server.
INPUTS: TemplateId / TemplateAlias / TemplateModel / InlineCss / From
INPUT CONTRACTS
Know what the action needs before it runs.
get_bounces
countOPTIONAL- Number of results to return per request.
offsetOPTIONAL- Number of results to skip before returning the current page.
typeOPTIONAL- Filter by bounce type.
inactiveOPTIONAL- Whether to return only inactive bounces.
emailFilterOPTIONAL- Filter by bounced email address.
create_template
NameREQUIRED- Template name.
SubjectOPTIONAL- Subject content for the template. Required for standard templates.
HtmlBodyOPTIONAL- HTML body content of the template.
TextBodyOPTIONAL- Plain-text body content of the template.
TemplateTypeOPTIONAL- Template type recognized by the official Postmark API.
validate_template
SubjectOPTIONAL- Subject content to validate against Postmark template syntax.
HtmlBodyOPTIONAL- HTML body content to validate.
TextBodyOPTIONAL- Plain-text body content to validate.
TestRenderModelREQUIRED- Additional upstream fields returned by Postmark.
InlineCssForHtmlTestRenderOPTIONAL- Whether CSS blocks should be inlined when rendering HTML test output.
edit_template
templateIdOrAliasREQUIRED- Template ID or template alias accepted by the Postmark path parameter.
NameREQUIRED- Updated template name.
SubjectOPTIONAL- Updated template subject content when the template is standard.
HtmlBodyOPTIONAL- Updated HTML body content.
TextBodyOPTIONAL- Updated plain-text body content.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Bounces
Get Postmark bounces for the current server with optional filters. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_bouncesControl Create Template
Create a Postmark template. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_templateVerify with Get Outbound Message Details
Get detailed content and events for one outbound Postmark message. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_outbound_message_detailsSAFETY BOUNDARY
Operate Postmark with explicit limits
- Authorize Postmark with API key and grant only the provider access required by the selected actions.
- 5 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Postmark rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Postmark task completed successfully.
CONNECTION MODEL
API key
Postmark server token used with the X-Postmark-Server-Token header. Find it under Server > API Tokens: https://postmarkapp.com/support/article/1008-what-are-the-account-and-server-api-tokens.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 6
- WRITE SIGNALS
- 5
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 1
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Postmark.