http provider documentation
🏬Self-hosted⛓️💥APIs➕Feature Request❓Question👟Actions
Use-case: I'm currently building out a 'production-ready-template' which I plan to use for all my new personal/client projects going forward - including 1 pending client project.
I've used zitadel managed login v1 in the past and wasn't happy with how little control I had over the flow - so this time I'm building out my auth flows manually and using the zitadel API to interact with zitadel and keep it as the auditable single source of truth for AuthN.
This time I want full control over the auth implementation - login pages and configuration are all mostly there, now I'm focussing on setting up the email system with full control over sending, templating, and formatting that I own.
Environment: Self hosting - but open to cloud
Version: v4.13.1
Stack:
Self hosted Zitadel
NestJS backend
NestJS "notifications" microservice
Next.js frontend
RabbitMQ
I'm tried experimenting with the zitadel api and webhooks to try and capture events which would require an email to be sent.
Unfortunately things like email verification codes are encrypted so the webhooks can't just send them on for my services to handle.
I started digging and found that http providers is an option (for sms for some reason) but it's not very well documented. Searching github issues documentation was mentioned as WIP but I can't find it.
I could do with some pointers for where I can find the right typings. Even if it's just a pointer at the protobufs that would be great.
Plus some thoughts on how 'stable' this whole http thing is. Whether I'm building on sand or not.
What you expected to happen: Easy (ish) integration with zitadel notifications for custom http provider
What went wrong: Can't find documentation or specs for what the different notifications types are and what their payloads are.
Attachments:
https://github.com/zitadel/zitadel/issues/7658#issuecomment-2352618261
https://zitadel.com/docs/guides/manage/customize/notification-providers
I've used zitadel managed login v1 in the past and wasn't happy with how little control I had over the flow - so this time I'm building out my auth flows manually and using the zitadel API to interact with zitadel and keep it as the auditable single source of truth for AuthN.
This time I want full control over the auth implementation - login pages and configuration are all mostly there, now I'm focussing on setting up the email system with full control over sending, templating, and formatting that I own.
Environment: Self hosting - but open to cloud
Version: v4.13.1
Stack:
Self hosted Zitadel
NestJS backend
NestJS "notifications" microservice
Next.js frontend
RabbitMQ
I'm tried experimenting with the zitadel api and webhooks to try and capture events which would require an email to be sent.
Unfortunately things like email verification codes are encrypted so the webhooks can't just send them on for my services to handle.
I started digging and found that http providers is an option (for sms for some reason) but it's not very well documented. Searching github issues documentation was mentioned as WIP but I can't find it.
I could do with some pointers for where I can find the right typings. Even if it's just a pointer at the protobufs that would be great.
Plus some thoughts on how 'stable' this whole http thing is. Whether I'm building on sand or not.
What you expected to happen: Easy (ish) integration with zitadel notifications for custom http provider
What went wrong: Can't find documentation or specs for what the different notifications types are and what their payloads are.
Attachments:
https://github.com/zitadel/zitadel/issues/7658#issuecomment-2352618261
https://zitadel.com/docs/guides/manage/customize/notification-providers
Configure SMTP, SMS (Twilio), and HTTP webhook providers to manage how ZITADEL sends notifications.
GitHub
Preflight Checklist I could not find a solution in the existing issues, docs, nor discussions I have joined the ZITADEL chat Describe your problem Example: http://sms-proivider/get?to=number&te...
