Appearance
Postmark
Send transactional emails, manage templates, track bounces, and configure webhooks with the Postmark API.
| Detail | Value |
|---|---|
| Category | Communication |
| Base URL | https://api.postmarkapp.com |
| Authentication | API Key |
| Endpoints | 8 |
| Connector key | email |
Using Postmark in a workflow
- Go to Connections and click New Connection.
- Pick Postmark from the marketplace.
- Enter your credentials (see Authentication above for what's expected).
- In a workflow, drop an API Call node and select this connection.
- Pick the operation you need from the Operation dropdown — the full list is below.
Available endpoints
| Endpoint | Summary |
|---|---|
POST /email | Send a single email |
POST /email/batch | Send a batch of up to 500 emails |
POST /email/withTemplate | Send an email using a saved template |
GET /bounces | Retrieve bounce records |
GET /templates | List all email templates |
POST /templates | Create a new email template |
GET /messages/outbound | Search sent outbound messages |
GET /stats/outbound | Get outbound delivery statistics |
Each endpoint is documented in full below. Use the outline on the right to jump to one.
POST /email
Send a single email
| Detail | Value |
|---|---|
| Operation ID | email.send |
| Method | POST |
| Path | /email |
Parameters
No parameters.
Request Body
| Field | Type |
|---|---|
From | string |
To | string |
Subject | string |
HtmlBody | string |
TextBody | string |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Postmark connection from the Connection dropdown.
- In the Operation dropdown, select
email.send. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked — fill them or the call will fail at runtime.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Postmark API reference.
POST /email/batch
Send a batch of up to 500 emails
| Detail | Value |
|---|---|
| Operation ID | email.sendBatch |
| Method | POST |
| Path | /email/batch |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Postmark connection from the Connection dropdown.
- In the Operation dropdown, select
email.sendBatch. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Postmark API reference.
POST /email/withTemplate
Send an email using a saved template
| Detail | Value |
|---|---|
| Operation ID | email.sendWithTemplate |
| Method | POST |
| Path | /email/withTemplate |
Parameters
No parameters.
Request Body
| Field | Type |
|---|---|
TemplateId | integer |
TemplateModel | object |
From | string |
To | string |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Postmark connection from the Connection dropdown.
- In the Operation dropdown, select
email.sendWithTemplate. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked — fill them or the call will fail at runtime.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Postmark API reference.
GET /bounces
Retrieve bounce records
| Detail | Value |
|---|---|
| Operation ID | email.listBounces |
| Method | GET |
| Path | /bounces |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
count | query | integer | No |
type | query | string | No |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Postmark connection from the Connection dropdown.
- In the Operation dropdown, select
email.listBounces. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Postmark API reference.
GET /templates
List all email templates
| Detail | Value |
|---|---|
| Operation ID | email.listTemplates |
| Method | GET |
| Path | /templates |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Postmark connection from the Connection dropdown.
- In the Operation dropdown, select
email.listTemplates. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Postmark API reference.
POST /templates
Create a new email template
| Detail | Value |
|---|---|
| Operation ID | email.createTemplate |
| Method | POST |
| Path | /templates |
Parameters
No parameters.
Request Body
| Field | Type |
|---|---|
Name | string |
Subject | string |
HtmlBody | string |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Postmark connection from the Connection dropdown.
- In the Operation dropdown, select
email.createTemplate. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked — fill them or the call will fail at runtime.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Postmark API reference.
GET /messages/outbound
Search sent outbound messages
| Detail | Value |
|---|---|
| Operation ID | email.searchOutbound |
| Method | GET |
| Path | /messages/outbound |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
count | query | integer | No |
recipient | query | string | No |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Postmark connection from the Connection dropdown.
- In the Operation dropdown, select
email.searchOutbound. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Postmark API reference.
GET /stats/outbound
Get outbound delivery statistics
| Detail | Value |
|---|---|
| Operation ID | email.getStats |
| Method | GET |
| Path | /stats/outbound |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Postmark connection from the Connection dropdown.
- In the Operation dropdown, select
email.getStats. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Postmark API reference.