nice-room-70150
09/18/2025, 7:01 PMtall-airline-16756
09/18/2025, 7:01 PMtall-airline-16756
09/18/2025, 7:02 PMredis.address field in your LiveKit config file. Just a heads-up, this option isn’t available on LiveKit Cloud.
For use cases where you need Redis integration—like building external services that respond to LiveKit events—I’d recommend exploring LiveKit’s WebHook callbacks or the Agent framework. These tools can interact with your own Redis instance separately from the LiveKit Cloud backend, giving you the connectivity you need.
Sources: pkg/service/wire.go | Deploying LiveKit | LiveKit Docs | Self-hosting the Ingress Service | LiveKit Docsnice-room-70150
09/18/2025, 8:18 PMtall-airline-16756
09/18/2025, 8:18 PMWebhookEvent payload that includes helpful details such as the room name, participant identity, and the type of event.
If you want to retrieve user information from your own database or Redis, here are a couple of friendly tips:
• Use the participant_joined event as your trigger. The event payload will have the participant’s Identity, which you can use to look up their info in your database or Redis.
• Another neat option is to include user-specific data directly in the participant’s Identity string or the participant attributes field when they join the room. This way, the webhook gets the data right away, so you don’t need to do extra lookups.
To keep things secure, webhook requests come with a signed JWT token in the Authorization header. You can use LiveKit’s WebhookReceiver libraries (available in Node.js, Go, Python, Rust) to easily validate and decode the payload.
If you’d like, I’m here to provide more details or examples to help you get this set up smoothly. Just let me know!
Sources: Webhooks | LiveKit Docs | examples/webhook.py | livekit-api/src/webhooks.rs | examples/webhooks-nextjs/pages/api/webhook.ts | webhook/notifier.go