Get Contact Properties
mailjet.get_contact_data
ActionEmailconnection required
Calls the Mailjet API with the connection's credentials.
Read the custom property values stored against one contact.
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 |
|---|---|---|---|---|---|
contact The contact to act on: Mailjet's numeric contact id, or the contact's email address. | string | Yes | — | — | jane@example.com |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"contact": "jane@example.com"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
contact_id Mailjet's numeric id for the contact. | string | — |
data Mailjet's raw property entries, each {"Name", "Value"}. | array | — |
properties The same properties as a flat object keyed by property name. | object | — |
{
"contact_id": "",
"data": [],
"properties": {}
}See Get Contact Properties 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.