ClickSend icon

ClickSend

Consume Clicksend API

Actions7

  • Send Fax Actions
  • Send Letter Actions
  • Send MMS Actions
  • Send Postcard Actions
  • Send SMS Actions
  • Send SMS to a contact List Actions
  • Send Voice Actions

Overview

This node integrates with the ClickSend API to send SMS messages. It allows users to send SMS either directly to a single recipient or to a contact list. This is useful for automating communication workflows such as sending notifications, alerts, marketing messages, or reminders via SMS.

Practical examples:

  • Sending appointment reminders to customers.
  • Broadcasting promotional SMS campaigns to a contact list.
  • Sending verification codes or alerts to individual phone numbers.

Properties

Name Meaning
Sender name/From field The number or alpha tag (name) from which the SMS is sent. If left blank, messages are sent from a shared number. You can select from your dedicated numbers or alpha tags linked to your account.
Recipient number / To field The phone number of the message recipient. Must be in local or international format (e.g., +61411111111). Required when sending to an individual.
Message body The content of the SMS message. A standard SMS supports up to 160 characters.
Schedule Optional date and time to schedule the message for future delivery. If not set, the message is sent immediately.
Custom String An optional reference string (max 50 characters) that you can use to track or identify the message.
Name or ID of contact list When sending SMS to a contact list, specify the name or ID of the list. The list must exist in your ClickSend account.

Output

The node outputs a JSON array containing the response from the ClickSend API for each send operation. The structure includes:

  • response_code: Indicates success or failure of the request.
  • data: Contains details about the queued messages, including counts and statuses.
  • In case of errors like invalid recipient or insufficient credit, the output contains an object with status and reason fields explaining the issue.

Example output snippet on success:

{
  "response_code": "SUCCESS",
  "data": {
    "queued_count": 1,
    "messages": [
      {
        "status": "SUCCESS",
        "message_id": "abc123"
      }
    ]
  }
}

If the recipient number is invalid:

{
  "status": "INVALID_RECIPIENT",
  "reason": "That number doesn't look quite right. Check it and try again."
}

If there is insufficient credit:

{
  "status": "INSUFFICIENT_CREDIT",
  "reason": "You don't have enough credit to send. Top up your account."
}

No binary data is output by this node.

Dependencies

  • Requires an API key credential for authenticating with the ClickSend API.
  • The node makes HTTP requests to ClickSend endpoints to send SMS messages.
  • No additional environment variables are required beyond the API authentication setup.

Troubleshooting

  • Invalid recipient error: Occurs if the phone number format is incorrect or unsupported. Ensure the number is in correct local or international format (e.g., +61411111111).
  • Insufficient credit error: Indicates the ClickSend account does not have enough balance to send the message. Resolve by topping up the account credit.
  • Scheduling issues: If scheduling a message, ensure the date/time is valid and in the future.
  • Empty sender field: Leaving the sender field blank uses a shared number, which may affect deliverability or branding. Use a dedicated number or alpha tag for better control.
  • API authentication failures: Verify that the API key credential is correctly configured and has necessary permissions.

Links and References

Discussion