Send SMS
mailjet.send_sms
ActionEmailconnection required
Calls the Mailjet API with the connection's credentials.
Send one SMS through Mailjet's v4 SMS API, using the SMS token on the connection rather than the email API key.
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 |
|---|---|---|---|---|---|
to Recipient number in international format, e.g. +33600000000. | string | Yes | — | — | +33600000000 |
text The message body to send to the handset. | string | Yes | — | — | — |
sender Sender name shown on the handset; overrides the connection's default SMS sender. | string | No | — | — | AcmeOps |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"sender": "AcmeOps",
"to": "+33600000000"
}Output
One shape.
result
The provider's response object, as returned.
Extra keys beyond the ones listed can appear.
{}Notes
- The SMS API is authenticated with a Bearer token generated in the SMS section of the Mailjet account — the email API key and secret do not work here.
- The response is Mailjet's own SMS object, including its nested delivery status, cost and message id.
See Send SMS 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.