Actions7
Overview
This node integrates with the ClickSend API to send SMS messages specifically to a contact list. It allows users to send bulk SMS campaigns by selecting a predefined contact list from their ClickSend account and composing a message to be sent to all contacts in that list. The node supports scheduling messages for future delivery and optionally setting a custom sender ID or phone number.
Common scenarios where this node is beneficial include:
- Marketing campaigns targeting a specific group of customers.
- Notifications or alerts sent to a team or department.
- Event reminders or announcements to a subscriber list.
Practical example: A business wants to notify all members of their loyalty program about an upcoming sale. They select the relevant contact list, write the promotional message, optionally set a sender name, and schedule the message to be sent at a specific time.
Properties
| Name | Meaning |
|---|---|
| Sender name/From field | The number or alpha tag (name) from which the SMS will be sent. If left blank, messages are sent from a shared number. Options are dynamically loaded from your dedicated numbers or alpha tags in ClickSend. |
| Name or ID of contact list | The identifier or name of the contact list to which the SMS will be sent. This must be selected from existing lists in your ClickSend account. |
| Message body | The content of the SMS message to send. Standard SMS length is 160 characters. |
| Schedule | Optional date and time to schedule when the message should be sent. If not set, the message is sent immediately. |
| Custom String | An optional reference string up to 50 characters, used as a custom identifier or note for the message. |
Output
The node outputs a JSON array containing the response from the ClickSend API after attempting to send the SMS messages. The structure includes:
response_code: Indicates success or failure of the request.data:queued_count: Number of messages queued for sending.messages: Array with details per message including status.
If the message is successfully queued, the output confirms this. If there is an error such as an invalid recipient number or insufficient credit, the output contains an object with a status field describing the error and a human-readable reason.
No binary data is output by this node.
Example successful output snippet:
[
{
"response_code": "SUCCESS",
"data": {
"queued_count": 10,
"messages": [
{
"status": "QUEUED"
}
]
}
}
]
Example error output snippet:
[
{
"status": "INVALID_RECIPIENT",
"reason": "That number doesn't look quite right. Check it and try again."
}
]
Dependencies
- Requires an active ClickSend account with API access.
- Needs an API key credential configured in n8n for authenticating requests to ClickSend.
- Contact lists and sender IDs must be pre-configured in the ClickSend dashboard.
- Internet access to call ClickSend REST API endpoints.
Troubleshooting
- Invalid Recipient Error: Occurs if the contact list contains improperly formatted phone numbers. Verify that all numbers are in correct international format.
- Insufficient Credit Error: Indicates the ClickSend account does not have enough balance to send messages. Top up your ClickSend account to resolve.
- Empty Contact List: If no contacts exist in the selected list, no messages will be sent. Confirm the list has valid contacts.
- API Authentication Failures: Ensure the API key credential is correctly set up and has necessary permissions.
- Scheduling Issues: Scheduled times must be valid ISO date strings; otherwise, messages may fail to queue.