CribScore
Back to docs

Examples

Webhook Automation Recipes

CribScore already exposes a signed webhook endpoint. This guide packages the low-friction recipes for insurer, benefits, and relocation teams that want alerts in their existing systems first.

Register the webhook once

The API contract stays unchanged. Register a facility-specific callback URL with the standard `/v1/webhooks` route, then fan out or transform the signed payload in your own automation layer.

  • CribScore sends JSON as `{ "event": "...", "payload": { ... } }`.
  • Every delivery includes `X-CribScore-Signature` and `X-CribScore-Event` headers.
  • Starter mappings live under `/automation/*` so docs, examples, and imports stay crawlable.

Slack, Teams, and email relays

Use an inbound webhook or lightweight relay to turn score, license, or violation events into operational alerts. The same CribScore payload can drive Slack text, Teams message cards, or an email relay without changing upstream delivery.

n8n, Zapier, and Make

If you do not want to maintain a relay, start with a webhook trigger in n8n, Zapier, or Make. The starter files in this repo show the first field mappings so ops teams can move from raw payloads to usable notifications quickly.

Support channel

Public questions and integration feedback route through GitHub Discussions at https://github.com/musa8026/CribScore/discussions.

Create Webhook Subscription

curl -X POST "https://api.cribscore.co/v1/webhooks" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "facility_id": "FACILITY_ID",
    "callback_url": "https://automation.example.com/cribscore",
    "events": ["score_change", "license_change"]
  }'

Template Files

Starter templates:
- https://www.cribscore.co/automation/slack-incoming-webhook.json
- https://www.cribscore.co/automation/teams-webhook.json
- https://www.cribscore.co/automation/email-relay.json
- https://www.cribscore.co/automation/n8n-starter.json

Related guides