ClickSend icon

ClickSend

Consume ClickSend API
Join our community

Actions8

Overview

The ClickSend MMS "Send MMS" operation node allows you to send multimedia messages (MMS) via the ClickSend API. This is useful for automating the delivery of images, GIFs, or other media files to recipients' mobile phones. Common scenarios include marketing campaigns, notifications with rich content, or sending personalized media messages to customers.

Practical examples:

  • Sending promotional images to a list of subscribers.
  • Delivering appointment reminders with attached documents or images.
  • Notifying users with animated GIFs or infographics.

Properties

Name Type Meaning
Media File URL String URL of the media file to be sent. If conversion is needed, use the node's upload operation first.
MMS Messages Collection Array of MMS message objects, each representing a message to send.
└ Subject String Subject line for the MMS (max 20 characters).
└ From String Sender ID; if empty, defaults to the API key owner's sender ID.
└ Body String The main text content of the MMS message.
└ To String Recipient's phone number in E.164 format (e.g., +61411111111).
└ Source Name String Method/source of sending (e.g., 'wordpress', 'php', 'c#').
└ Schedule DateTime Optional scheduled time for delivery; leave blank for immediate sending.
└ Custom String String Custom reference string returned with replies and delivery reports.
└ List ID Number List ID for bulk sending; can be used instead of specifying individual recipient numbers.
└ Country Code String ISO alpha-2 country code (e.g., "US"); used to format recipient number if not in international format.

Output

The node returns a JSON object containing the response from the ClickSend API after attempting to send the MMS messages. The structure typically includes:

{
  "http_code": 200,
  "response_code": "SUCCESS",
  "data": [
    {
      "message_id": "string",
      "to": "string",
      "status": "string",
      "custom_string": "string"
      // ...other fields as provided by ClickSend
    }
  ],
  "messages": [
    // Details about each message sent
  ]
}
  • If binary data is involved (e.g., uploading media), it is referenced by its URL, not included directly in the output.

Dependencies

  • External Service: Requires a ClickSend account and valid API credentials.
  • n8n Credentials: Must configure clickSendApi credentials in n8n.
  • Environment: Internet access to reach https://rest.clicksend.com/v3.

Troubleshooting

Common Issues:

  • Invalid Media File URL: Ensure the media file URL is accessible and points to a supported file type.
  • Missing Required Fields: All required fields (such as "To", "Body", "Subject") must be filled for each message.
  • Authentication Errors: Check that your ClickSend API credentials are correct and active.
  • Incorrect Phone Format: The "To" field must be in E.164 format; otherwise, provide a valid "Country Code".

Error Messages & Resolutions:

  • "401 Unauthorized": Invalid API credentials. Re-enter your ClickSend API key and username.
  • "400 Bad Request": Missing or invalid parameters. Double-check all required fields and formats.
  • "415 Unsupported Media Type": The media file type is not supported. Use a compatible file format (e.g., JPEG, PNG, GIF).

Links and References

Discussion