ClickSend - Send an SMS to a list

Use the ClickSend - Send an SMS to a list action A tool for building the processes, logic, and direction within workflows. to send an SMS message to a ClickSend list.

For more information about ClickSend, go to ClickSend.

Configure the ClickSend - Send an SMS to a list action

  1. Add the action to the workflow and open the action configuration panel. For more information, see Add, rename, and copy actions.

  1. Select a Connection. If you do not have a connection, see Add a connection.
  2. In Messages, click Add item.
  3. Specify the To list contact list ID.
  4. Specify the From sender ID.
  5. Specify the Message content.
  6. Configure the details of the SMS, such as country, source, your reference, schedule time, and a custom reply-to email address.
  7. If you want to add more SMSs messages to send, click Add item again and configure the message.
  8. Create or select a variable for the output.

For more information on all the required and optional configuration fields, go to ClickSend - Send an SMS to a list action fields and settings.

ClickSend - Send an SMS to a list action fields and settings

Section

Field

Description

Variable types

(Unlabeled)

Connection Credentials and other settings required to pass data between the workflow and the indicated service, which could be a cloud service, business application, or content store.

The ClickSend connection to use to send the SMS message.

To refresh the available connections, click .

(n/a)

Messages Message Click Add item to create a new SMS message to send. (n/a)
  To list

Your contact list ID.

You can post to a list with up to 20000 recipients with each action. The response is far less detailed than the normal ClickSend - Send an SMS action.

Text, Decimal, Integer, Boolean, DateTime, Collection
  From Your sender ID. This is the number that shows on the recipient's phone when they receive the message. Text, Decimal, Integer, Boolean, DateTime, Collection
  Message

The text of your message.

A standard SMS message has a maximum of 160 characters. Longer messages are definitely possible, however exceeding 160 characters creates a ‘second’ message. The end user will see this as one long message on their handset. When a message is longer than 160 characters, this is referred to as a multi-part message as it contains multiple messages (or multiple-parts). The total SMS limit then becomes 153 characters per ‘part’ as the 7 characters are used up by invisible headers and footers which denote which part of the message is being sent. If a message contains any characters that aren't in the GSM 03.38 character set, the message type will be treated as Unicode. See How many characters can I send in a message for more information.

You are required to add an opt-out message to the end of your message body if you are sending a marketing message. This can be in the form of asking users to reply STOP to opt-out or by including StopMsg.me/xxxxx which is a placeholder that will add a link that can be clicked to out-out.

Text, Decimal, Integer, Boolean, DateTime, Collection
  Source Your method of sending the message, for example; 'nintex', 'wordpress', 'php', 'c#'. Text, Decimal, Integer, Boolean, DateTime, Collection
  Your reference A description of the SMS message for your future reference. Text, Decimal, Integer, Boolean, DateTime, Collection
  Schedule

Leave this field blank for immediate delivery. Your scheduled time in Unix time format.

Text, Decimal, Integer, Boolean, DateTime, Collection
  Country The ISO alpha-2 character country code e.g. 'US', This used to format the recipient number if it's not in international format. Text, Decimal, Integer, Boolean, DateTime, Collection
  Custom reply-to email address An email address where the reply should be emailed to. If omitted, the reply will be emailed back to the user who sent the outgoing SMS. Text, Decimal, Integer, Boolean, DateTime, Collection
Output Sent message details

Stores the result of the action as an object. See ClickSend API for more details. The following values are returned:

  • HTTP response code: (Integer)
  • Response Code: (Text)
  • Response message: (Text)
  • Data: (Object)
    • Queued count: (Integer)
    • Total price: (Decimal)
    • Total count: (Integer)
    • Messages: (Collection)
      • Body: (Text)
      • Carrier: (Text)
      • Country: (Text)
      • Your reference: (Text)
      • Date: (Integer)
      • Direction: (Text)
      • From: (Text)
      • Message ID: (Text)
      • Message parts: (Integer)
      • Message price: (Decimal)
      • Schedule: (Decimal)
      • Status: (Text)
      • Sub account ID: (Integer)
      • To: (Text)
      • User ID: (Integer)
    • Currency: (Object)
      • Currency: (Text)
      • Currency name: (Text)
      • Currency prefix c: (Text)
      • Currency prefix d: (Text)
Object