Kolinea webhooks: your tools told as soon as a folder moves
What you do from webhooks
Be told when a folder is opened, updated, duplicated, closed or reopened
Be told when a client answers a request, gives an approval, fills in a form or makes a choice
Be told when a document arrives, is accepted or rejected, and when an appointment is confirmed
Follow requests: handling declared, extension requested then accepted or refused, due date changed
Choose, address by address, which events to receive
Connecting webhooks, step by step
In your workspace settings, under Developers, add the HTTPS address that will receive the deliveries.
Choose the events to receive, then keep the signing secret in your tool.
Send a test from the same page, and check the signature of every delivery before handling it.
Told instead of asking
A tool that wants to know whether a client has answered can query the API every five minutes. It is slow, and almost every call comes back empty. With a webhook, Kolinea tells your tool when the thing happens: a document received, a request handled, a folder closed.
You choose the useful events address by address. One address can receive only the documents that arrive, another everything about appointments. Each address has its own signing secret, so a tool that receives deliveries checks they come from Kolinea before acting on them.
Deliveries that carry nothing sensitive
Each delivery holds only identifiers and the link to the object concerned. Your tool reads the details back through Kolinea’s API, with its key: it only reads what that key is allowed to read. An intercepted delivery holds no name and no message.
A confidential publication triggers no delivery, and neither does the document uploaded in answer to it.
What your tools can listen to
The events follow the folder’s life. On the folder: opened, updated, handed to another lead, duplicated, closed or reopened. On participants: added, removed, access changed. On requests: an answer, a refusal, an approval, a choice, a form filled in, handling declared, an extension requested then accepted or refused. On documents: received, accepted or rejected. And confirmed appointments, milestones reached, contacts created or updated.
A log for every address
Kolinea keeps a record of each delivery: its date, its result, the new attempts. A failed delivery is retried with a growing delay, and you can replay it by hand once your tool is fixed. A test, sent from the same page, checks that a new address answers.
The rest of what the API can do with a folder is described on the API and integrations page.
What the integration does not do
A delivery holds identifiers only, never a name, an e-mail or a text: your tool reads the details back through the API, with its key and within its rights.
A confidential publication, and the document that answers it, trigger no delivery.
The same event can arrive more than once, and deliveries do not always arrive in order: your tool recognises a duplicate by its webhook-id header.
Only HTTPS addresses are accepted.
The features involved
Your questions before connecting
Another question? Contact us
Every delivery is signed the Standard Webhooks way: webhook-id, webhook-timestamp and webhook-signature headers, an HMAC-SHA256 signature with the address’s secret. You can change that secret at any time.
Kolinea retries the delivery, with a delay that grows at each attempt. The delivery log keeps every attempt, and you can replay a delivery from that log.
For security reasons, a delivery carries no name, no e-mail address and no text. Your tool reads the message through the API, with a key that has the right to.
The full list, with the meaning of each, is in the API documentation and in the form for adding an address.
Other integrations
Your next folder, with nothing lost along the way
Not the right time?
Get the link by e-mail and pick up later, from your computer.
One e-mail only, and your address is not kept.