Skip to content
Docs
MCP & integrations / Webhooks
View as Markdown ↗
View this page as plain text
Open app

Webhooks

See Overview for how webhooks differ from MCP and the REST API.

What webhooks do

Webhooks let Colabra push activity to your own systems in real time.

Use them when you want downstream systems to react to project activity without polling:

  • trigger notifications
  • sync data into another system
  • kick off follow-up automation

This is the right surface when Colabra should notify your software that something changed. It is not the right surface when your software needs to ask Colabra questions on demand or mutate state directly.

A downstream workflow reacts to project changes

Real deal example: outbound event, then API follow-up

A team wants its internal ops system to know when new files, tasks, or comments appear in a live deal. A webhook can deliver the event immediately. If the downstream system then needs more detail or wants to write back, it can call the REST API using the event payload as the trigger.

Webhook settings

The product surface lets you:

  • enable or disable webhooks
  • set the destination URL
  • choose event families
  • use the generated signing secret

Signing secrets use the whsec_... format.

Event families

Event families exposed in the product:

  • projects
  • tasks
  • comments
  • files
  • Use webhooks to trigger your own process quickly.
  • Verify signatures with the generated whsec_... secret before trusting payloads.
  • Fetch more detail from the API if your downstream step needs a richer resource shape than the webhook event carries.

Use webhooks for outbound notifications to your system. Use the REST API when you need to fetch or mutate Colabra data directly.