We would like to use different webhook endpoints for our DEV and PROD environments, but currently use a single workspace.
Is it possible to set up multiple webhooks for one workspace (for example, one for DEV and one for PROD) through custom support or an additional setup?
This would help us separate our environments without needing to duplicate workspaces.
Thanks for your guidance or any help you can provide!
Hey @tsunechan! This isn’t supported today but we do want to support more webhook endpoints per workspace.
A few questions:
Are you using commit tags to differentiate prompts in your prod and dev environments or are dev/prod different prompts?
Do you want the webhook endpoint that’s used to be configured up front per prompt (or per prompt commit tag if you’re using those)? Example: Prompt A is a dev prompt and any changes to prompt A should always trigger webhook endpoint A
Yes, we use commit tags (dev and prod) to differentiate prompts in our environments.
Yes, that’s exactly what we want.
If prompt A has a new commit with a dev or prod tag, we’d like the change to trigger either endpoint A-dev or endpoint A-prod, depending on the tag.
We’re going to be adding support for a webhook notification when prompt tags are changed this week actually. While that doesn’t completely satisfy your use case, for now, you could use this to get notified when tags change and then set up your own endpoint to route to dev/prod endpoints. Longer term we plan to add native support for this functionality!