ZITADEL self-hosted server — Action (v2) not firing when new user is created
Hi everyone, I need some help.
I’m currently running a self-hosted ZITADEL server. I’ve created an Action (v2)(event: all, target: webhook) with the purpose of calling a webhook whenever a new user is created.
However, the Action doesn’t seem to work.
When checking the logs, I don’t see any trigger for the action.
I’m using version v4.3.1.
I’ve also tried other versions — v3.3.0, v2.x.x — but still no result.
Even when running locally in Docker, the situation is the same.
Please help me. Thanks!
15 Replies
Hi @koankem, I'm an AI assistant for ZITADEL. While a team member reviews this question, I'll see if I can find relevant sources for your question.
Answer
I wasn't able to find a direct answer, here are some relevant sources:
1. Testing Actions V2 with Webhook.site (1) : This guide explains how to set up Actions V2 with webhook targets and includes CORS configuration requirements for local testing.
2. V2 Actions silently fail and ignore scheme for http targets. (2) : This discusses an issue where Actions V2 targets require HTTPS endpoints and silently fail with HTTP targets.
**
To learn more, see the sources I considered:
[1] Testing Actions V2 with Webhook.site
[2] V2 Actions silently fail and ignore scheme for http targets.
Feel free to tag @Ask Inkeep with additional questions.
Got it. Tagging @Rajat for additional help.
hey @koankem can you please share your target code that you wrote that you thought will trigger the action?.
I created a target and attached it to an action with the event set to either "all" or "user.human.added".
@Rajat pls take a look.
@FFO @Rajat @Mridang Agarwalla anyone can help me?
hey @koankem I will take a look at it tomorrow, apologies for the delay as I got stuck with other questions
hey @koankem can you pls change your action type to REQUEST and select the service
/zitadel.user.v2.UserService/AddHumanUser and see if it works. I cant see your
and try creating a human user and see if your actions triggers or not
okay I said tomorrow well I think it could be an easy fix but you can inform me
@Rajat It’s still not working. I’ve checked the logs but couldn’t find any monitoring logs related to the HTTP call.
hey @koankem do you see anything on your
target endpoint server file that is running at /health?. You can add all kind of logs in that
You can try writing a very simple listener and test it against your instance to check and verify if actions are not working or your listener needs to be changed/updated.@Rajat Of course I do! That’s the project’s health check API. I also checked both the server logs and the Cloudflare logs, but there’s no record of any API call. Could there be an issue with the self-hosted server?
Additionally, I’m currently setting up the target and action through the UI. Is it mandatory to use the ZITADEL API for this version?
if you are setting up actions in CloudFlare, you may need a signing key that you have to pass as your env variables for production. You can read about it here
Please let me know if this helps.
GitHub
actions/actions-v2-cloudflare-workers/deployment-utility/README.md ...
ZITADEL Actions - Easy extensibility with custom code. Think GitHub Actions in an Identity System. - zitadel/actions
You’re probably misunderstanding — I’m only using a Cloudflare Tunnel to expose my local API.
hey @koankem we are not aware about any major breakdown of actions v2 as of right now. I followed the example above and it works 🙂
so I am getting lost as to what could be broken for you
I’m currently running a self-hosted ZITADEL server version v4.3.1. When I test, I’m using the ZITADEL Docker setup. Are there any environment configuration notes I should be aware of? @Rajat
not that I know of, did you try just reproducing the example and if that worked?. Because I still dont know if you tried that or not?.
I can only test it on Monday when I have more bandwidth but still reaching out to see if I can get more info on your use case to test.