# Kolinea webhooks: your tools told as soon as a folder moves

> A document arrives, a client answers, a folder is closed: Kolinea notifies your tool’s address, with a signed delivery that holds identifiers only.

## 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](/en/integrations/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](/en/features/api-and-integrations) page.

## What you can do

- 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

## Setup

1. In your workspace settings, under Developers, add the HTTPS address that will receive the deliveries.
2. Choose the events to receive, then keep the signing secret in your tool.
3. Send a test from the same page, and check the signature of every delivery before handling it.

## Limits

- 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.