Webhooks & Zapier Integration

clariBI integrates with external automation services through a Zapier webhook receiver. Use this to connect clariBI events to hundreds of other apps via Zapier or similar webhook-based automation tools.

Zapier Integration

clariBI provides a webhook receiver endpoint that accepts data from external services. To connect clariBI with Zapier, use the Webhooks by Zapier action to POST to your clariBI webhook URL. clariBI is not listed as an official app in the Zapier marketplace, so you configure the integration using Zapier's generic webhook connector.

How It Works

Configure an external service (such as Zapier) to send HTTP POST requests to your clariBI webhook URL. The payload should be JSON and include the relevant event data. clariBI processes the incoming webhook and triggers the appropriate action.

Example Payload

{
  "event": "report.completed",
  "timestamp": "2026-02-24T10:30:00Z",
  "data": {
    "report_id": 42,
    "title": "Q4 Revenue Analysis",
    "status": "completed",
    "url": "https://claribi.com/app/reports/42"
  },
  "organization_id": 7
}

Automation Examples

Common automation examples using generic webhook tools:

• Send Slack messages when reports complete
• Add rows to Google Sheets when data syncs
• Create Jira tickets when goals fall behind
• Send email digests of weekly reports

Security

Webhook payloads include a signature header (X-ClariBI-Signature) that you can verify to ensure the request came from clariBI. The signature is an HMAC-SHA256 of the payload using your webhook secret.

Retry Policy

If your endpoint returns a non-2xx status, clariBI retries up to 3 times with exponential backoff (1 min, 5 min, 30 min). After 3 failures, the webhook is marked as failing and you receive an email notification.

Related

• API Overview
• Authentication