mirror of
https://github.com/andwati/zitadel.git
synced 2026-10-18 05:52:51 +00:00
Wim Van LaerandGitHub
9b064d8b74
# Which Problems Are Solved - Typos - Punctuation - Markdown table formatting - ... (A bunch of issues my editor gave) # How the Problems Are Solved # Additional Changes # Additional Context
27 lines
1.2 KiB
Plaintext
27 lines
1.2 KiB
Plaintext
---
|
|
title: ZITADEL Actions
|
|
sidebar_label: Actions
|
|
---
|
|
|
|
An Identity and Management system is a very interactive place. ZITADEL has built in functionality to react to its events. This functionality is called **Actions** and can be accessed from your organizations top navigation.
|
|
|
|
<img
|
|
src="/docs/img/guides/console/actionsmenu.png"
|
|
width="700px"
|
|
alt="Actions menu"
|
|
/>
|
|
|
|
Actions allow you to define scripts which are then run on certain triggers.
|
|
To add an action, click at the **new** button and provide a script and a name.
|
|
You can specify a timeout and whether the action is allowed to fail too.
|
|
|
|
<img src="/docs/img/guides/console/action.png" alt="Create Action" width="450px" />
|
|
|
|
To run those scripts, a flow with a trigger has to be created.
|
|
This could for example be an **External Authentication** Flow, with a **Post Authentication** trigger.
|
|
|
|
<img src="/docs/img/guides/console/flow.png" alt="Flow" width="400px" />
|
|
|
|
Now whenever a user gets authenticated externally with an IDP, an action is triggered after the authentication itself.
|
|
If you want to know more where actions can be useful, take a look at the feature [here](/concepts/features/actions) or directly jump to an example of a custom behavior [here](/guides/manage/customize/behavior).
|