ZITADEL Actions v2 | ZITADEL Docs

ZITADEL Actions v2

By using ZITADEL Actions v2, you can modify ZITADEL's behavior on specific API calls, events, or functions. This is useful when you have special business requirements that ZITADEL does not support out-of-the-box.

Why Actions?

ZITADEL can't anticipate or solve every possible business rule and integration requirement for all users. Here are some examples:

With Actions, ZITADEL provides a way to address such scenarios.

How it works

There are three necessary components:

The process is that, at certain points, ZITADEL executes a defined Execution, which then calls the defined Target(s). This allows everyone to implement custom behavior for as many processes as needed.

Possible conditions for the Execution:

Currently, defined Actions v2 will be executed in addition to Actions.

Migration

Further reading

Example use cases:

The following repository contains various examples demonstrating how to use Actions v2 in different scenarios. It also includes a deployment script for testing the examples with Cloudflare Workers: