Webhooks

Webhooks let Tormano push events to systems we don't have a built-in connector for.

Outgoing webhooks

Tormano POSTs to an external URL when something happens. Two ways to configure:

1. As a global subscription — Settings > Integrations > Webhooks lets you add an endpoint (URL), pick which events it should receive, and get a POST for every matching event.
2. As an automation action — a workflow can include a Trigger webhook action that POSTs to a URL you provide when the workflow runs.

The payload is JSON. Supported events include contact.created, contact.updated, contact.deleted, deal.created, deal.stage_changed, deal.won, deal.lost, donation.created, donation.updated, activity.created, company.created, grant.created, grant.awarded, and more — you tick the ones you want per endpoint.

Authentication

Every outgoing webhook is signed with HMAC-SHA256 in the X-Tormano-Signature header. Verify it on your side using the signing secret shown when you create the endpoint.

Retry behavior

If the receiver returns an error or doesn't respond, Tormano retries up to 3 times with exponential backoff. Recent deliveries and their response status are shown under each endpoint on the Webhooks page.

Receiving data into Tormano

There is no in-app screen for creating an "incoming webhook" endpoint, and the Automation builder has no inbound-webhook trigger. To push data into Tormano programmatically, use the REST API with an API key (see "REST API and API keys").