Stable URLs for Webhook Handlers in Preview?
I'm using httpActions for webhooks (e.g., Clerk) to centralize backend logic and logging in Convex. This is great for dev/prod, but Preview Deployments create a challenge: their dynamic URLs require manual webhook endpoint updates in services like Clerk for each new preview.
My questions:
Stable Preview Webhook URL: Is there a Convex-native way to get a stable URL for webhooks that routes to the current active preview deployment, without needing third-party tunnelers (e.g., ngrok)?
Logging Strategy: If I use a Next.js API route for a stable URL, this splits logs between Vercel and Convex. What are best practices for managing this or achieving more centralized logging in Convex for the entire webhook flow?
Looking for community insights, established patterns, or info on any planned features that could help with:
- Stable webhook ingress for dynamic preview environments.
- Better log consolidation if part of the webhook is handled externally.
Any advice on managing webhooks with preview deployments for a clean, observable setup would be fantastic. Thanks!
1 Reply
Thanks for posting in <#1088161997662724167>.
Reminder: If you have a Convex Pro account, use the Convex Dashboard to file support tickets.
- Provide context: What are you trying to achieve, what is the end-user interaction, what are you seeing? (full error message, command output, etc.)
- Use search.convex.dev to search Docs, Stack, and Discord all at once.
- Additionally, you can post your questions in the Convex Community's <#1228095053885476985> channel to receive a response from AI.
- Avoid tagging staff unless specifically instructed.
Thank you!