FYes, the actions v1 have an http module https://zitadel.com/docs/apis/actions/modules#http which you should be able to trigger post registration https://zitadel.com/docs/apis/actions/internal-authentication#post-creation
Also as inspiration an example http call https://github.com/zitadel/actions/blob/main/examples/make_api_call.js
Also as inspiration an example http call https://github.com/zitadel/actions/blob/main/examples/make_api_call.js
EHi ffo. Is there any way to trigger an event when a user updates his/her information? Or when it is deleted? Also, does this work when an user is created using the API?
FThats actually something we are looking into for actions v2.
Actions v2 can already intercept API calls to Zitadel but we do not (yet) send the events (registration, deletion, ...).
There is a ready issue for this subject though https://github.com/zitadel/zitadel/issues/7246 which means we will work on it sooner or later
Actions v2 can already intercept API calls to Zitadel but we do not (yet) send the events (registration, deletion, ...).
There is a ready issue for this subject though https://github.com/zitadel/zitadel/issues/7246 which means we will work on it sooner or later
EHi, thanks for the pointer. Meanwhile, which could be an alternative? I need to sincronize N relational databases with user's ID and full name... Thanks again.
FHm, you could call the events-api to fetch that data from. How much eventual consistency can you tolerate?
EI ended up firing async events from my app