Actions8
- Account Actions
- SMS Actions
- MMS Actions
- Upload Actions
Overview
The ClickSend node's "MMS → Calculate MMS Price" operation allows you to estimate the cost of sending one or more MMS (Multimedia Messaging Service) messages before actually dispatching them. This is useful for budgeting, previewing costs for bulk campaigns, or validating message configurations prior to sending.
Common scenarios:
- Marketing teams estimating campaign costs before launch.
- Developers integrating ClickSend with n8n to automate pricing checks for dynamic message batches.
- Businesses wanting to validate recipient numbers and message content for compliance and cost control.
Example:
A user wants to send a batch of promotional MMS messages and needs to know the total price before proceeding. They provide the media file URL and an array of message details; the node returns the calculated price.
Properties
| Name | Type | Meaning |
|---|---|---|
| Media File URL | String | URL of the media file to be sent. Use the upload operation first if conversion is required. |
| MMS Messages | Collection | Array of MMS messages to calculate the price for. Each message includes the following fields: |
| └ Subject | String | Subject line (max 20 characters) for the MMS message. |
| └ From | String | Sender ID. If left empty, defaults to the API key owner's sender ID. |
| └ Body | String | The main text content of the MMS message. |
| └ To | String | Recipient phone number in E.164 format (e.g., +61411111111). |
| └ Source Name | String | Method/source of sending (e.g., 'wordpress', 'php', 'c#'). |
| └ Schedule | DateTime | Scheduled time for delivery (leave blank for immediate). |
| └ Custom String | String | Custom reference string returned with replies and delivery reports. |
| └ List ID | Number | List ID for sending to a group instead of a single recipient. |
| └ Country Code | String | ISO alpha-2 country code (e.g., "US") for formatting recipient numbers. |
Output
The node outputs a JSON object containing the calculated price(s) for the provided MMS message(s). The structure typically includes:
{
"price": <number>,
"currency": "<string>",
"messages": [
{
"to": "<recipient>",
"price": <number>,
"status": "<string>"
}
// ...more messages
]
}
price: Total estimated price for all messages.currency: Currency code (e.g., "USD").messages: Array with per-message pricing and status.
Note: Actual output fields may vary depending on the ClickSend API response.
Dependencies
- External Service: Requires a ClickSend account and valid API credentials (
clickSendApi). - n8n Configuration: Credentials must be set up in n8n under the name
clickSendApi. - Internet Access: Node must be able to reach
https://rest.clicksend.com/v3.
Troubleshooting
Common Issues:
- Invalid Media File URL: Ensure the URL is accessible and points to a supported media type.
- Missing Required Fields: All required fields (e.g., "To", "Body", "Subject") must be filled for each message.
- Authentication Errors: Make sure your ClickSend API credentials are correct and active.
- Incorrect Phone Format: Recipient numbers should be in E.164 format unless using a list ID.
Error Messages & Resolutions:
"401 Unauthorized": Check your API credentials in n8n."400 Bad Request": Review input fields for missing or invalid data (e.g., subject too long, missing recipient)."Media file not found": Verify the media file URL is correct and publicly accessible.