Skip to content
Notis

Keep optimized asset URLs in Jira current

Give teams a dependable link to the current optimized version when they open the ticket for an asset.

Trigger

Recurring schedule

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

Action

Edit Issue

Updates an existing jira issue with field values and operations. supports direct field parameters (summary, description, assignee, priority, etc.) that are merged with the fields parameter. direct parameters take precedence.

Why this helps

Tickets may point to outdated or less useful asset URLs after transformation changes.

  • Keep useful transformed asset links near Jira work.
  • Reduce confusion between original and delivery-ready versions.
  • Save time locating the right URL.

Setup

Build it in a few focused steps.

  • 1Connect Cloudinary and Jira once in the Notis portal.
  • 2Create an automation in Automations, New Automation, and name it.
  • 3Tell Notis which issues and Cloudinary transformations to use, then update the issue description with the available optimized URL.
  • 4Pick a recurring schedule and choose where run reports should go.
  • 5Test with one asset and its related Jira issue.

Questions about this workflow

Can Notis create any transformation?

Use transformation options supported by Cloudinary and available through your connection. Specify the desired transformation in your instruction.

How does it find the Jira issue?

The issue should contain a Cloudinary asset reference or another matching identifier that Notis can retrieve.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

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

Cloudinary triggers

Jira actions

Recurring trigger

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

TriggerScheduled

Add Attachment

Uploads and attaches a file to a jira issue.

ActionInstant

Webhook trigger

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

TriggerInstant

Add Comment

Adds a comment using atlassian document format (adf) for rich text to an existing jira issue.

ActionInstant

Add Watcher to Issue

Adds a user to an issue's watcher list by account id.

ActionInstant

Assign Issue

Assigns a jira issue to a user, default assignee, or unassigns; supports email/name lookup.

ActionInstant

Bulk Create Issues

Creates multiple jira issues (up to 50 per call) with full feature support including markdown, assignee resolution, and priority handling.

ActionInstant

Create Issue

Creates a new jira issue (e.g., bug, task, story) in a specified project.

ActionInstant

Link Issues

Links two jira issues using a specified link type with optional comment.

ActionInstant

Create Project

Creates a new jira project with required lead, template, and type configuration.

ActionInstant

Connect any two apps with Notis in the middle.

Cloudinary and Jira, 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 Jira.