Bulk Manage List Contacts
mailjet.manage_many_contacts
ActionEmailconnection required
Calls the Mailjet API with the connection's credentials.
Queue a batch of contacts to be added to, removed from or unsubscribed from one list. Mailjet processes this asynchronously and answers with a job id.
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
3 fields, 2 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 |
|---|---|---|---|---|---|
contacts The contacts to manage, as a JSON array of {"Email", "Name", "Properties"} objects. | array | Yes | — | array of object | [{"Email":"jane@example.com","Name":"Jane"}] |
action What to do with the membership: addforce subscribes even a previously unsubscribed contact, addnoforce leaves that unsubscribe in place, remove deletes the membership and unsub marks it unsubscribed. | string | Yes | — | one of "addforce", "addnoforce", "remove", "unsub" | addnoforce |
list_id Numeric id of the Mailjet contact list. Falls back to the list on the connection when left blank. | string | No | — | — | 10012345 |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"action": "addnoforce",
"contacts": [
{
"Email": "jane@example.com",
"Name": "Jane"
}
],
"list_id": "10012345"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
job_id Mailjet's id for the queued job — the batch is not applied yet. | string | — |
queued True when Mailjet accepted the batch as a job. | boolean | — |
list_id The list the batch will be applied to. | string | — |
action The action the batch will apply. | string | — |
contact_count How many contacts were submitted. | number | — |
result The record Mailjet returned for the call. | object | — |
{
"action": "",
"contact_count": 0,
"job_id": "",
"list_id": "",
"queued": false,
"result": {}
}Notes
- This call is asynchronous: a job id means Mailjet accepted the batch, not that the contacts are on the list yet.
See Bulk Manage List Contacts 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.