Skip to content
Notis

Turn a folder change request into a Cloudinary update

When a ticket is updated with a clear folder move or rename request, Notis can update the Cloudinary folder and report what happened.

Trigger

Updated Issue

Fires when an existing issue is changed in the Jira project you configure — for example its status, assignee, or any other field on the issue is updated. Only issues in that project produce an event. It does not fire on comment activity: adding, editing, or deleting a comment on an issue will not produce an event from this trigger.

Action

Update Folder

Tool to rename or move an existing asset folder. use when you need to change the folder's name or location.

Why this helps

Folder change requests can sit in tickets while someone remembers to make the corresponding Cloudinary update.

  • Carry a stated folder change request into Cloudinary from the updated issue.
  • Keep the request and resulting folder update connected.
  • Get a run report to review the action.

Setup

Build it in a few focused steps.

  • 1Connect Jira and Cloudinary once in the Notis portal.
  • 2Create an automation in Automations, New Automation, or tell Notis from any channel.
  • 3Ask Notis to update a Cloudinary folder only when the updated issue clearly states its current folder and requested new name or location.
  • 4Pick Jira's Updated Issue trigger and choose where run reports go.
  • 5Test with one real issue containing a specific folder change request.

Questions about this workflow

Will it infer the folder change from any issue update?

No. The issue needs to state the current folder and requested name or location clearly. The workflow should report when those details are missing.

Can it move a folder if the destination does not exist?

The update action renames or moves an existing folder. The requested destination and folder details need to be clear and supported by Cloudinary.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

Notis builds workflows that link Jira to Cloudinary. A trigger fires from one place; an action lands in another.

Jira triggers

Cloudinary actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

Create Folder

Tool to create a new asset folder. use when you need to organize assets into nested directories. use after confirming the folder path does not already exist.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

Create Metadata Field

Tool to create a new metadata field definition. use when extending your metadata schema with new fields.

ActionInstant

New Issue

Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.

TriggerInstant

Create Trigger

Tool to create a new webhook trigger for a specified event type. use after configuring your webhook endpoint and choosing the event type. example: "create a trigger for uploads to https://example.com/hooks/cloudinary"

ActionInstant

New Project

Triggered when a new project is added in Jira

TriggerInstant

Create Upload Mapping

Tool to create a new upload mapping folder and url template. use when you need to dynamically map external url prefixes to a cloudinary asset folder before uploading files.

ActionInstant

Updated Issue

Fires when an existing issue is changed in the Jira project you configure — for example its status, assignee, or any other field on the issue is updated. Only issues in that project produce an event. It does not fire on comment activity: adding, editing, or deleting a comment on an issue will not produce an event from this trigger.

TriggerInstant

Create Upload Preset

Tool to create a new upload preset. use when defining centralized upload options (tags, formats, transformations, etc.) before asset uploads.

ActionInstant

Delete Derived Resources

Tool to delete derived assets. use when you need to remove specific derived assets by their ids. example: "delete derived assets with ids [id1, id2]".

ActionInstant

Delete Metadata Field Datasource Entries

Tool to delete datasource entries for a specified metadata field. use when you need to soft-delete (inactivate) specific entries in a field's datasource. example prompt: "delete entries ['color1','color2'] from metadata field 'color id'"

ActionInstant

Delete Folder

Tool to delete an empty asset folder. use when the folder is confirmed empty and you need to remove it.

ActionInstant

Connect any two apps with Notis in the middle.

Jira and Cloudinary, or any other combination from 1,000+ integrations.

When this happens · Trigger

Do this · Action

Save your first hour today.

7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Cloudinary.