Skip to main content

ClickSend integration

Send SMS, MMS, campaigns, and letters and react to inbound replies and delivery receipts on behalf of your clients.

What it does

The ClickSend integration lets your agency drive a client's outbound messaging program from inside a workflow. Connect a client's ClickSend account once and your workflows can send transactional or marketing SMS, MMS attachments, and physical letters through the v3 REST API. You can also run SMS and MMS campaigns against a contact list, manage contact lists and contacts, look up the connected account balance, page through message history, and react in real time when ClickSend posts an inbound SMS reply or a delivery receipt.

ClickSend no longer sells Voice, Fax, or Postcards, so TaskJuice ships no actions for them — see Withdrawn products.

Connect a ClickSend account

  1. Open your workspace in TaskJuice and add a ClickSend connection from the ClickSend node in the workflow editor.
  2. In a new tab, sign in at dashboard.clicksend.com as the client, or as your agency if the client has delegated key creation to you.
  3. Click API Credentials at the top right of the dashboard.
  4. Copy the account username, which is the email or username used to sign in, and create an API key.
  5. Paste the username and API key into TaskJuice. Both values are sent as HTTP Basic credentials on every request.

To rotate or revoke the key, return to the API Credentials panel, generate a new key, and update the TaskJuice connection.

Triggers

  • clicksend/inbound-sms fires when ClickSend posts an inbound SMS reply. One POST carries one inbound message.
  • clicksend/sms-delivery-receipt fires when ClickSend posts an SMS delivery receipt, carrying the message id, status, and any custom string echoed back from the original send.
  • clicksend/inbound-sms-polled polls ClickSend's inbound message listing on a schedule and emits one activation per cycle. Use this when you cannot create a rule in the ClickSend dashboard.
  • clicksend/sms-delivery-receipt-polled polls the delivery receipt listing on a schedule and emits one activation per cycle.

The two polled triggers wrap each cycle's new records in an items array. Add a Loop node with arrayPath set to items when you want to act on each record individually, or read the array directly for a digest.

Set up a push trigger

The two webhook triggers publish an inbound URL. Create a matching rule in ClickSend:

  1. Copy the inbound URL from the trigger in TaskJuice.
  2. In the ClickSend dashboard, open Inbound SMS Settings for replies, or Delivery Receipts for receipts.
  3. Add a rule with Action set to URL and paste the inbound URL as the address.
  4. For inbound SMS, leave the payload format at its default, or set it to JSON or GET.

All three payload formats work. POST sends form-encoded fields, JSON sends a JSON body, and GET sends the same fields as query parameters. All three carry an identical field set, so the choice does not change what your workflow receives.

Inbound SMS rules match on a dedicated number. If the client has not rented one, use the polled triggers instead.

Actions

Messaging

  • clicksend/send-sms sends one or more SMS messages, with optional sender id, scheduled delivery, and a custom string that is echoed back on delivery receipts.
  • clicksend/send-mms sends one or more MMS messages with a media attachment. The media must already be hosted at a publicly reachable URL.
  • clicksend/send-sms-campaign sends an SMS campaign to an entire contact list, with optional scheduling.
  • clicksend/send-mms-campaign sends an MMS campaign to an entire contact list.

Direct mail

  • clicksend/send-letter prints and posts a physical letter from a hosted PDF to one or more recipients.
  • clicksend/list-return-addresses lists the account's saved return addresses. Each letter recipient requires a return_address_id, and this action is how a workflow discovers one.

Contacts

  • clicksend/create-contact-list creates a new contact list scoped to the connected account.
  • clicksend/delete-contact-list deletes a contact list and every contact in it.
  • clicksend/list-contact-lists lists the account's contact lists.
  • clicksend/search-contact-lists searches contact lists by free-text query.
  • clicksend/add-contact adds a contact to an existing contact list. Only a phone number is required.
  • clicksend/get-contact retrieves a single contact from a list.
  • clicksend/update-contact updates a contact's details in place.
  • clicksend/delete-contact removes a contact from a list.
  • clicksend/list-contacts pages through every contact in a list.

Reads

  • clicksend/get-account retrieves the connected account profile, including the live balance and trial status.
  • clicksend/get-sms-history pages through outbound SMS history, optionally filtered by date range and free-text search.
  • clicksend/list-inbound-sms pages through inbound messages received by the account.

Each list action uses ClickSend's page and limit pagination, which caps at 100 records per page.

Known limitations

  • Per-account rate limits, daily message caps, sender id restrictions, and pricing are governed by the client's ClickSend plan, not by TaskJuice. When ClickSend returns a 429, the action surfaces as a retryable rate-limit error.
  • ClickSend does not sign webhook deliveries. Its rule form accepts a URL and a payload format and offers no header field, so there is no signature, timestamp, or shared secret on an inbound POST. The inbound URL is the only credential, so treat it as a secret and rotate the trigger if it leaks.
  • Sender id rules vary by country. Alphanumeric sender ids work in many regions but are blocked in the United States and Canada, where a dedicated number is required.
  • Trial accounts prefix every outbound SMS body with ClickSend: and are restricted to United States and Canada destinations.
  • Send SMS accepts an array of messages, and ClickSend bills each recipient individually. Read total_price from the response to confirm spend before triggering follow-up steps.
  • Letters are billed per item and consume account credit on every send.

Withdrawn products

ClickSend has stopped selling Voice, Fax, Postcards, and Transactional Email to new customers. Accounts opened after each sunset receive a hard 403 on the corresponding endpoints, and there is no dashboard toggle or support request that restores them — the products are simply no longer offered.

These actions were removed from the catalog on 2026-09-01. They are gone rather than hidden: every one of them returned a hard 403 on a newly opened account, so shipping them could only ever produce a failing workflow.

Removed actionWithdrawn product
clicksend/send-voiceVoice
clicksend/list-voice-historyVoice
clicksend/send-faxFax
clicksend/send-postcardPostcards

The 403 was confirmed against a live account, including on an empty request body — the test that separates a permission gate from a payload error. If ClickSend ever reinstates a product, the action returns by restoring its definition to the catalog seed.

Letters are unaffected despite ClickSend's help centre grouping them with postcards: POST /v3/post/letters/send still succeeds on a newly opened account, so clicksend/send-letter remains fully supported.

TaskJuice ships no Transactional Email actions for ClickSend. Clients who need email should use a dedicated provider.

Was this helpful?