Overview
This node integrates with a telephony service to send SMS or MMS messages. It allows users to specify the sender phone number, recipient phone number, and message content to dispatch text messages programmatically within an n8n workflow. This is useful for automating notifications, alerts, marketing campaigns, or any scenario requiring outbound SMS communication.
For example, you could use this node to:
- Send appointment reminders to customers.
- Dispatch verification codes via SMS.
- Notify team members of critical system events.
Properties
| Name | Meaning |
|---|---|
| From Number Name or ID | The phone number from which the SMS or MMS will be sent. Choose from a list of available numbers or specify an ID using an expression. |
| To Number | The recipient's phone number to which the SMS or MMS will be sent. |
| Content | The text content of the SMS message to be sent. |
Output
The node outputs JSON data representing the result of the send operation for each input item. Each output item contains the response from the telephony service indicating success or failure of the SMS/MMS sending action.
If an error occurs during sending and "Continue On Fail" is enabled, the output will include an error field describing the issue for that particular item.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for authenticating with the telephony service.
- The node dynamically loads available sender phone numbers via an API call.
- No additional environment variables are explicitly required beyond the API authentication setup.
Troubleshooting
Common issues:
- Invalid or missing sender phone number: Ensure the "From Number" is selected from the loaded options or correctly specified via expression.
- Incorrect recipient phone number format: Verify the "To Number" is in a valid international format.
- API authentication errors: Confirm the API key credential is correctly configured and has necessary permissions.
Error messages:
- Errors returned from the telephony API will be surfaced in the node output under an
errorproperty if "Continue On Fail" is enabled. - If not continuing on fail, the node execution will stop and throw an error indicating the cause (e.g., invalid parameters, network issues).
- Errors returned from the telephony API will be surfaced in the node output under an
Links and References
- n8n Expressions Documentation
- Telephony service API documentation (refer to your specific provider's docs for details on phone number formats and messaging limits)