Webhooks are automated HTTP messages that Cinode sends to a URL you choose whenever something you're watching changes — a project created, a candidate updated, an employee deleted. They let you connect Cinode to external services in real time, without polling the API for changes.
You configure webhooks yourself from Cinode's Administration area: pick the objects and actions to watch, give Cinode an endpoint URL to call, and Cinode starts sending a message the moment a matching event happens.
Webhooks is a licensable module. If you don't see Webhooks under Administration > Integrations, ask your Customer Success representative to enable it. Company Admin permission is required to add or edit a webhook.
What a webhook message contains
Every webhook watches a combination of objects and actions that you choose when you set it up.
Objects and actions you can watch
Choose one or more of these objects:
Employee
Customer
Customer contact
Project
Project role
Candidate
Subcontractor
Public announcement
Partner network announcement
Absence
Project assignment request
Project assignment request response
Event
and one or more of these actions: Created, Updated, or Deleted — or All to cover everything. A single webhook can combine several objects and actions; add more webhooks if you need different endpoints for different combinations.
Every message includes an audit trail, not just the data
Each delivery is an HTTP POST with a JSON body made up of:
Metadata — which object changed, which action fired, and, where relevant, which part of it changed (for example a property, a pipeline stage, or a team membership).
The object itself — the current state of the affected record. On a Deleted action there is no current state to send, so this is left empty.
Who made the change — included when Cinode can identify the user; left out otherwise.
Every request also carries a unique delivery ID in its X-Cinode-Webhook-Delivery-Id header. This ID stays the same across retries of the same delivery, so your endpoint can use it to detect and ignore a message it has already processed.
Why your team needs it
Webhooks remove the need to poll Cinode for changes — your systems find out the moment something happens.
Sync data with your CRM. Keep customer or project data aligned with your CRM the moment it changes in Cinode.
Real-time notifications. Alert the right people in Slack, Microsoft Teams, or similar tools when a project is marked as Won or a pipeline stage changes.
Trigger ERP processes. Kick off invoicing or onboarding workflows the moment a project is won.
Build on your own timeline. Your team and developers build and maintain the integration, so it fits exactly how you work. If you'd rather not build it yourself, Cinode can assist at an additional cost — contact your Customer Success representative.
Secure and reliable by design
Webhooks are built to fail safely and tell you when something needs attention.
Optional authentication. Require the receiving endpoint to authenticate the request with HTTP Basic Auth by setting a username and password when you configure the webhook. Leave this empty if your endpoint doesn't need it.
Endpoint checks. Cinode rejects endpoint URLs that point to loopback addresses or hosts that can't be resolved, both when you save a webhook and before every delivery.
Automatic retries. If your endpoint doesn't respond with a success status, Cinode retries the delivery with increasing delays between attempts, up to 10 attempts in total.
Automatic disabling after repeated failures. If all 10 attempts fail, Cinode turns the webhook off and emails whoever created or last edited it, so it doesn't keep failing silently. Re-enable it from the Webhooks page once your endpoint is fixed.
Setting up a webhook
Go to Administration > Integrations > Webhooks.
Click Add your first webhook.
Select the objects and actions to watch, from the list above.
Enter your Endpoint URL and, if your endpoint needs it, a Basic Auth username and password. Leave these fields empty if not needed.
Toggle the webhook on to activate it.
To change a webhook later, click the three dots next to it and choose Edit.
Frequently asked questions
What happens if my endpoint is down or returns an error?
Cinode retries the delivery automatically, with increasing delays between attempts, up to 10 attempts. If every attempt fails, the webhook is turned off automatically and an email is sent to whoever created or last edited it. Fix your endpoint, then re-enable the webhook from the Webhooks page — it does not turn itself back on.
How do I avoid processing the same message twice?
Use the X-Cinode-Webhook-Delivery-Id header. It stays the same across every retry of the same delivery, so you can use it to recognize and skip a message you've already handled.
What authentication does Cinode support?
HTTP Basic Auth is the only authentication method available today. Set a username and password when you configure the webhook, and Cinode sends them with every request to that endpoint.
Can I build more advanced integrations?
Yes. Combine webhooks with the Cinode REST API to read more data or make changes back in Cinode when a webhook fires. If you need help building or maintaining an integration, contact your Customer Success representative — Cinode can assist at an additional cost.