Actions3
- Message Actions
Overview
This node integrates with the Solapi messaging service to send various types of messages, focusing here on sending text messages (SMS/LMS/MMS). It supports sending messages to multiple recipients simultaneously, specifying sender IDs, and optionally including subjects or images for multimedia messages. This node is useful in scenarios such as marketing campaigns, notifications, alerts, or any automated system that needs to send text-based communications programmatically.
For example, you can use this node to:
- Send SMS alerts to a list of customers about an upcoming event.
- Dispatch promotional MMS messages with images to subscribers.
- Notify users via SMS about account activities or password resets.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authentication: "OAuth2" or "API Key (HMAC-SHA256)" |
| To | Recipient phone numbers; multiple numbers separated by commas or new lines |
| From (Registered Sender ID) Name or ID | The registered sender ID or name from which the message will be sent |
| Text | The content of the text message |
| Subject | Optional subject line for the message (used mainly for LMS/MMS) |
| Image ID (Optional) Name or ID | Optional image identifier for sending MMS messages |
| Country Code | Country dialing code for the recipient numbers (default is "82" for South Korea) |
Output
The node outputs JSON data containing the response from the Solapi API after attempting to send the messages. The structure typically includes details about each message's delivery status, message IDs, and any errors encountered.
Example output JSON structure (simplified):
{
"messageId": "string",
"status": "string",
"to": "recipient number",
"error": "optional error message"
}
If multiple recipients are specified, the output contains an array of such objects under a messages or similar field.
No binary data output is produced by this operation.
Dependencies
- Requires access to the Solapi messaging API.
- Supports two authentication methods:
- OAuth2 token-based authentication.
- API key authentication using HMAC-SHA256 signatures.
- Requires configuration of appropriate credentials in n8n for either OAuth2 or API key.
- Uses internal helper functions to make HTTP requests to Solapi endpoints.
Troubleshooting
- Invalid Authentication Errors: Ensure that the correct authentication method is selected and that the corresponding credentials (OAuth2 token or API key/secret) are properly configured in n8n.
- Invalid Phone Numbers: The "To" field must contain valid phone numbers formatted correctly without extra spaces or invalid characters. Use commas or new lines to separate multiple numbers.
- Missing Required Fields: The "From", "To", and "Text" fields are required. Omitting these will cause errors.
- Image ID Issues: If sending MMS with an image, ensure the image ID exists and is accessible in your Solapi storage.
- API Rate Limits or Quotas: Sending large volumes may hit Solapi limits; monitor API usage and handle errors accordingly.
- JSON Parsing Errors: When providing JSON strings (e.g., for buttons or variables in other operations), ensure they are well-formed.
Links and References
This summary focuses on the "Send Text Message" operation of the "Message" resource within the Solapi node.