Overview
This node acts as a webhook trigger for ClickSend events, specifically handling inbound SMS automation rules via webhooks. It allows users to create, check, and delete webhook subscriptions on the ClickSend platform that listen for incoming SMS messages matching a specified rule. When an SMS event occurs that matches the configured rule, the node receives the data and triggers the workflow.
Common scenarios include:
- Automating responses or workflows based on inbound SMS messages.
- Integrating SMS-based notifications or commands into business processes.
- Monitoring specific SMS content or sender patterns using custom rules.
For example, a user can set up a rule named "Support Requests" that triggers the workflow whenever an SMS containing certain keywords is received, enabling automated ticket creation or alerts.
Properties
| Name | Meaning |
|---|---|
| Rule Name | The name of the ClickSend inbound SMS automation rule to create or listen for. This defines which SMS messages will trigger the webhook. |
Output
The node outputs the JSON body of the incoming webhook request from ClickSend. This typically contains details about the inbound SMS event, such as message content, sender information, timestamps, and other metadata related to the SMS.
The output is structured as an array of JSON objects, each representing one inbound SMS event received by the webhook.
No binary data output is involved.
Dependencies
- Requires an API key credential for authenticating with the ClickSend REST API.
- Needs network access to ClickSend's API endpoints (
https://rest.clicksend.com/v3/automations/sms/inbound). - The node manages webhook lifecycle (create, check existence, delete) via authenticated HTTP requests to ClickSend.
- Proper configuration of the webhook URL in ClickSend is handled automatically by the node.
Troubleshooting
- Webhook not triggering: Ensure the API key credential is valid and has permissions to manage automations. Verify that the webhook URL is correctly registered in ClickSend.
- Rule creation failure: Check that the "Rule Name" property is provided and unique. API errors may occur if the rule name conflicts or if the account lacks required permissions.
- Webhook existence check fails: This might indicate the webhook was deleted externally or the stored webhook ID is invalid. Re-create the webhook by reactivating the trigger.
- API authentication errors: Confirm that the API key credential is correctly set up in n8n and has not expired or been revoked.