FerrisKey
← Modules

Event-Driven Extensibility

Webhooks

Pushes HTTP notifications to external systems when something happens in FerrisKey: a user created, a role assigned, a secret rotated. It bridges the identity layer to the rest of your stack.

Read the docs All modules

Covers

HTTP POSTEvent SubscriptionsCustom HeadersAuth HeaderReal-Time SyncCRM IntegrationSlack NotificationsPagerDutySIEM ForwardingLifecycle Events

Key capabilities

What Webhooks does for you.

  • 01

    Event Subscriptions

    Subscribe each webhook to the events it cares about: user.created, user.role.assigned, client.deleted, and 35 more.

  • 02

    Custom Headers

    Add Authorization, X-Webhook-Secret, or any custom header to authenticate deliveries at the receiving end.

  • 03

    Per-Realm Scope

    Webhooks are scoped to a realm. Each tenant can have its own set of endpoints and subscriptions.

  • 04

    Multiple Endpoints

    Register as many webhooks as needed. The same event fans out to all registered subscribers in parallel.

  • 05

    Last Triggered At

    Each webhook records when it last fired, which is what you want when debugging a silent integration.

  • 06

    Decoupled Design

    Your app reacts to identity events without polling FerrisKey. Clean event-driven integration.

How it works

From the first request to the result, in 4 steps.

  1. 1

    Register webhook

    Create a webhook with a target URL, optional custom headers, and a name. Scoped to a realm.

  2. 2

    Subscribe to events

    Add event subscriptions, choosing which lifecycle events should trigger the webhook.

  3. 3

    Event fires

    A matching event occurs in the realm. FerrisKey builds the payload and dispatches an HTTP POST.

  4. 4

    Your system responds

    Your endpoint receives the structured payload and reacts: send an email, sync a CRM, trigger a workflow.

Ready to use Webhooks?

Full reference, configuration options, and examples in the documentation.

Open docs

Other modules