Suppress Addresses
postmark.create_suppressions
ActionEmailconnection required
Calls the Postmark API with the connection's credentials.
Add up to 50 addresses to a message stream's do-not-send list, and report which of them Postmark accepted.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- API key
- Providers
- Postmark
- Secret shape
- the server API token, or {"server_token": "…"}
- Config it needs
- message_stream, from_address, base_url
- Resolved by
- config.connection_id, else node.connection_id
Configuration
2 fields, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
emails The addresses to suppress: a JSON array, or one comma-separated string. Postmark accepts at most 50 per call. | array | Yes | — | 1–50 characters; array of string | — |
message_stream The message stream to suppress on. Leave blank to use the stream on the connection, which defaults to Postmark's 'outbound' stream. | string | No | — | — | — |
Output
One shape.
result
| Field | Type | Example |
|---|---|---|
results One row per address, with Postmark's status and message for that address. | array | — |
succeeded How many addresses Postmark reported as done. | number | — |
failed How many addresses Postmark refused, each for its own reason. | number | — |
partial True when some addresses were done and others refused in the same call. | boolean | — |
{
"failed": 0,
"partial": false,
"results": [],
"succeeded": 0
}Notes
- An address Postmark refuses does not fail the step — read 'partial' and the per-address status.
See Suppress Addresses run in a workflow.
In a technical demo we add the Postmark connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.