Get Message History
mailjet.get_message_history
ActionEmailconnection required
Calls the Mailjet API with the connection's credentials.
List the delivery events recorded for one message — queued, sent, opened, clicked, bounced and so on.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- Username & password
- Providers
- Mailjet
- Secret shape
- {"username": "<public API key>", "password": "<private API key>"} (+ "sms_token" for the SMS API)
- Config it needs
- sender_email, sender_name, sms_from, contacts_list_id, 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 |
|---|---|---|---|---|---|
message_id Mailjet's numeric message id, as returned by a send in 'message_ids'. | string | Yes | — | — | 576460752303423999 |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"message_id": "576460752303423999"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
items The records Mailjet returned in this page. | array | — |
count How many records this page returned. | number | — |
total How many records match the query in total. | number | — |
{
"count": 0,
"items": [],
"total": 0
}See Get Message History run in a workflow.
In a technical demo we add the Mailjet connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.