updating and cloning a scenario and either re-using or creating a new webhook Pros and Cons??

[amazingjameso]

If i have a scenario that's running and a month down the road there is an update to the scenario. Normally for us, we develop and test in sandbox, then clone the scenario into prod and deactivate the old scenario. We re-use the same webhook that was on the old version. However, I've heard that its good to create a new webhook every time i clone an updated scenario over. But in doing this i've found out that if i deactivate the old scenario, the webhook on that version is still active and needs to be manually disabled, which is causing issues with data going to the new/old webhooks. Which is better re-use a webhook on the same scenario even if its updated or create a new webhook every time its updated and keep in mind to deactivate that one as well? what are the pros and cons of this?

Thanks!

[Sven-iX]

Personally I don't like the cloning to prod approach much, instead I export the JSON, import and the re-set the connections/hooks. In that case I keep the same hook.

If you clone - probably cleaner to create a new one, albeit with the caveat you mentioned.

[monicacardoso · Accepted solution]

Hi @amazingjameso, 

Thank you for your question! Here are the pros and cons of both approaches: 

Reusing the same webhook

✅ The URL doesn't change, so you don’t need to update external systems that send data to the webhook

✅ Avoids the risk of multiple active endpoints if only one webhook is used

✅ Easier to manage and track when you only have one webhook per event

❌ If not carefully managed, webhooks might point to deactivated or stale scenarios, causing failures or data loss

❌ If the new scenario fails, it’s harder to quickly revert if the same webhook is already reassigned

Creating new webhook 

✅ You can test new scenarios in parallel without impacting production

✅ Easier to isolate issues, compare outputs, and revert if needed

✅ Each version has its own webhook, making audits or logs clearer

❌ Deactivating the scenario does not deactivate the webhook; you must disable it separately or delete it 

❌ If both old and new webhooks are active, external systems may send duplicate data

❌ You must update external systems or forms to point to the new webhook URL 

My personal recommendation would depend on what you're doing. If you're just updating the logic in the production environment, I would reuse the existing webhook. If you're testing a significant logic change, I would create a new webhook. If you're doing some temporary testing and need to compare payloads, I would create a new webhook. 

- Monica