This is absolutely essential for any long term use of the custom webhook action in GHL workflows. I don't build new workflows in GHL because of this missing feature. If for example i have 10 workflows that use this custom webhook action I will most likely have 30+ different custom webhook actions across all of them.

The purpose of saving secret keys to GHL is to be able to reuse them easily, keep them private and secure, and to easily update them all at once if a key/token needs to be rotated or expires. In it's current state, when I rotate API keys i have to go into every single workflow and make sure I manually find every single action that uses the old key and update each one hoping that I don't miss any.

Today the only management of these keys is the ability to add a new key or delete an old key. I replaced GHL workflows with a different software that allows me to do this and I build all of my workflows there. If for example the other software (n8n) behaved the same way as GHL does with key management, every time that I rotated a key (expired, key compromised, enforced key rotation policy, etc.) I would have to go in and manually update 73 different workflow actions one by one. This key rotation process would only get worse with every additional workflow that I build.

GHL UI workflows are not useable or sustainable for large scale growth and integration with APIs and custom webhooks in their current state