Rename
Cloudinary rename notification. Payload fields depend on the triggering operation; all received fields are preserved.
Workflow template
Send editors the old and new public IDs as soon as an asset is renamed. Use the pair to find references to the old delivery URL and update them in your CMS. Connect Cloudinary and choose a private editorial topic.
How it works
Cloudinary rename notification. Payload fields depend on the triggering operation; all received fields are preserved.
Run the Send ntfy notification action in ntfy.
Before activation
Open the template in FastHook to create an editable Workflow Draft.
Connect your accounts for Cloudinary, ntfy.
Review the Steps, field mappings, routes, and provider settings.
Activate the Workflow when the Draft is ready, then verify a test run.
No. FastHook creates a disconnected Draft. Connect your own Cloudinary, ntfy accounts before activation.
Yes. The copied Workflow is an editable Draft. Review every Step, input, mapping, and route before you activate it.
FastHook recreates the Trigger configuration, Action Steps, routes, and mappings with new IDs. Provider accounts, credentials, and secrets are never copied.
Only after you connect the required accounts, finish the configuration, and explicitly activate the Draft.