mirror of
https://github.com/zitadel/zitadel.git
synced 2025-06-12 17:08:35 +00:00
065250a108
* chore(docs): fix links for domain migration * try trailing slash for netlify * trial * fix typo * test path * try preview proxied * test local proxy * try to define the domain with redirect to /docs * remove build commands * debug netlify router and fix image link * working config * fix analytics
26 lines
1.2 KiB
Plaintext
26 lines
1.2 KiB
Plaintext
---
|
|
title: 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 a **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, a 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 behaviour [here](/guides/manage/customize/behavior).
|