Cancel Scheduled Message
mandrill.cancel_scheduled
ActionEmailconnection required
Calls the Mandrill API with the connection's credentials.
Cancel a message that is scheduled but has not been sent yet.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- API key
- Providers
- Mandrill
- Secret shape
- the API key, or {"api_key": "…"}
- Config it needs
- base_url, from_email, from_name, subaccount, ip_pool
- 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 |
|---|---|---|---|---|---|
scheduled_id Id of the scheduled message, as returned by a send call or by the scheduled list. | string | Yes | — | — | — |
Output
One shape.
result
| Field | Type | Example |
|---|---|---|
_id Identifier of the scheduled message. | string | — |
created_at When the message was created, in UTC. | string | — |
send_at When the message is due to be sent, in UTC. | string | — |
from_email Sender address of the scheduled message. | string | — |
to Recipient address of the scheduled message. | string | — |
subject Subject line of the scheduled message. | string | — |
cancelled True once Mandrill has dropped the message. | boolean | — |
{
"_id": "",
"cancelled": false,
"created_at": "",
"from_email": "",
"send_at": "",
"subject": "",
"to": ""
}See Cancel Scheduled Message run in a workflow.
In a technical demo we add the Mandrill connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.