Webhooks and events

Two complementary event mechanisms let your systems react to Records Labs.

Outbound developer webhooks

Register HTTPS endpoints in Developers → Webhooks and Records Labs POSTs signed JSON events as they happen. Each endpoint has its own signing secret (shown once, rotatable); verify the X-Records-Labs-Signature header on every delivery before trusting the payload.

Available event types include API request completion/failure, MCP tool calls, article and Creation publishes, help-desk handoffs/replies/resolutions, CSAT ratings, and ingestion-run completions — the webhook editor lists the current set, and any type added later appears there automatically.

Automation event stream (Zapier / n8n / Make)

The /api/v1/automation subtree offers subscription management plus polling and a live SSE stream (GET /api/v1/automation/events) for automation platforms. It requires an organization key with the automation scope. GET /api/v1/automation/registry is the self-describing catalog of triggers and actions.

Inbound integration webhooks

The reverse direction also exists: Records Labs receives signature-verified webhooks from connected tools (Slack, Gmail, Drive, …) to keep your knowledge fresh. Those are configured per connection in Settings → Connectors, each with its own whsec_ signing secret — they are not part of the developer API.