Activate Bounced Address
postmark.activate_bounce
ActionEmailconnection required
Calls the Postmark API with the connection's credentials.
Reinstate an address Postmark deactivated after a bounce, so the server will send to it again.
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
1 field, 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 |
|---|---|---|---|---|---|
bounce_id The numeric Postmark id of the bounce that deactivated the address. | string | Yes | — | — | — |
Output
One shape.
result
| Field | Type | Example |
|---|---|---|
bounce_id The bounce that was acted on. | string | — |
message Postmark's wording for the outcome. | string | — |
inactive The address's state after the call; false means it can be sent to again. | boolean | — |
bounce The whole bounce record as Postmark returned it. | object | — |
{
"bounce": {},
"bounce_id": "",
"inactive": false,
"message": ""
}Notes
- A spam complaint cannot be reactivated: Postmark reports CanActivate false on those bounces and refuses the call.
See Activate Bounced Address 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.