Webhook-Driven Playbooks

Playbooks can be authored in any workflow system such as Powershell, n8n, Tines, or custom scripts via any available IDE, also with the help of generative AI. BalkanID's recommended approach is authoring playbooks via n8n. Authored playbooks can be version controlled in Github repositories. The whole development and deployment of playbooks can be automated via Github actions.

On the BalkanID side, the playbook integration model is an Outbound Webhook destination subscribed to one or more event topics (employee.created, request.actioned, campaign.completed, integration.sync, and so on). BalkanID pushes signed event payloads to any webhook URL when those topics fire. As long as the webhook URL stays stable across releases, the workflows (playbooks) behind it can be changed freely and managed via any repository management and CI/CD automation framework.

The older pattern of configuring a Playbook with a Server URL and triggering it manually from the Findings is still supported on some tenants, but the recommended path going forward is to subscribe an Outbound Webhook destination to the event topics you care about and let playbook react to those events. This document describes the newer path.

BalkanID's Outbound Webhooks feature (under Configure → Webhooks in your tenant) lets you register destinations that receive event payloads when things happen inside BalkanID. For more details on BalkanID Outbook Webhooks, refer here.