Cloudinary logo
ntfy logo

Workflow template

Catch broken image references after a Cloudinary rename

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

Workflow steps

1 Trigger · 1 Action
Cloudinary1 · Trigger

Rename

Cloudinary rename notification. Payload fields depend on the triggering operation; all received fields are preserved.

ntfy2 · Action

Send ntfy notification

Run the Send ntfy notification action in ntfy.

Before activation

Set up your workflow

  1. Copy the template

    Open the template in FastHook to create an editable Workflow Draft.

  2. Connect your accounts

    Connect your accounts for Cloudinary, ntfy.

  3. Review the Workflow

    Review the Steps, field mappings, routes, and provider settings.

  4. Activate

    Activate the Workflow when the Draft is ready, then verify a test run.

Questions about this template

Does the template copy someone else's credentials?

No. FastHook creates a disconnected Draft. Connect your own Cloudinary, ntfy accounts before activation.

Can I change the Steps and mappings?

Yes. The copied Workflow is an editable Draft. Review every Step, input, mapping, and route before you activate it.

What is copied into my workspace?

FastHook recreates the Trigger configuration, Action Steps, routes, and mappings with new IDs. Provider accounts, credentials, and secrets are never copied.

When does the Workflow start running?

Only after you connect the required accounts, finish the configuration, and explicitly activate the Draft.

Explore connected apps