Overview
The Cling Trigger node for n8n starts workflows when specific events occur in the Cling platform. It is designed to listen for webhook notifications from Cling, such as when a document is accepted, created, denied, sent, or viewed. This node is beneficial for automating processes that depend on real-time updates from Cling, such as sending notifications, updating records, or triggering follow-up actions based on document status changes.
Practical examples:
- Automatically notify a team when a document is accepted.
- Update a CRM record when a document is viewed by a client.
- Start an approval workflow when a new document is created in Cling.
Properties
| Name | Meaning |
|---|---|
| Authentication | Select the authentication method for connecting to Cling. Options: Basic Auth, Api Token |
| Event | Choose which Cling event should trigger the workflow. Options: Document Accepted, Document Created, Document Denied, Document Sent, Document Viewed |
Output
The node outputs a JSON object containing all fields received in the webhook body from Cling, with two additional fields for convenience:
- triggerEvent: The type of event that triggered the webhook (e.g.,
document.accepted). - createdAt: The timestamp when the event was created.
Example output:
{
"triggerEvent": "document.accepted",
"createdAt": "2024-06-01T12:34:56Z",
// ...other fields from the Cling webhook payload
}
Dependencies
- External Services: Requires access to the Cling API and valid credentials (either Basic Auth or API Token).
- n8n Configuration: The webhook URL must be accessible via HTTPS (not HTTP or www.), as required by Cling for webhook delivery.
- Credentials: You must set up either "clingCredentialsApi" or "clingCredentialsApiTokenApi" in n8n.
Troubleshooting
Invalid Webhook URL:
Error: "not a valid webhook URL, make sure to have an HTTPS url."
Solution: Ensure your n8n instance is accessible over HTTPS and not just HTTP or using a "www." prefix.Webhook Not Triggering:
Possible causes include incorrect event selection, missing or invalid credentials, or network/firewall issues preventing Cling from reaching your n8n webhook endpoint.404 Errors During Setup:
If the node cannot find an existing webhook subscription, it will attempt to create one. Ensure your credentials are correct and have sufficient permissions.