Overview
This node acts as a webhook trigger for ClickSend events, specifically handling inbound SMS messages via ClickSend's automation rules. It listens for incoming SMS messages that match a specified rule and triggers the workflow when such messages are received.
Common scenarios include:
- Automating responses or processing of inbound SMS messages.
- Integrating SMS-based notifications or commands into workflows.
- Monitoring specific SMS content or senders by defining rules in ClickSend.
For example, you can set up a rule to trigger this node whenever an SMS containing certain keywords arrives, enabling automated ticket creation or alerting systems.
Properties
| Name | Meaning |
|---|---|
| Rule Name | The name of the ClickSend inbound SMS automation rule to listen for. This identifies which SMS messages will trigger the webhook based on the configured rule in ClickSend. |
Output
The node outputs the JSON body of the incoming webhook request from ClickSend. This typically contains details about the inbound SMS message, such as sender, message content, timestamp, and other metadata.
The output is structured as an array of JSON objects under the json field, each representing one inbound SMS event.
No binary data output is involved.
Dependencies
- Requires an API key credential for authenticating with the ClickSend API.
- Needs network access to ClickSend's REST API endpoints.
- The node uses ClickSend's inbound SMS automation API to create, check, and delete webhook rules dynamically.
- Proper configuration of the webhook URL in ClickSend is handled automatically by the node.
Troubleshooting
- Webhook not triggering: Ensure the "Rule Name" matches an existing inbound SMS automation rule in your ClickSend account. Also verify that the workflow is active and the webhook URL is correctly registered.
- Authentication errors: Confirm that the API key credential is valid and has sufficient permissions to manage inbound SMS automations.
- Failed webhook creation: Check network connectivity and API limits. The node attempts to create the webhook rule on activation; failures here may prevent triggering.
- Unexpected payload format: If the incoming data structure changes, verify compatibility with the node’s expected JSON format.