Skip to content
Notis

Keep asset metadata current in Jira

Refresh the ticket context teams use to review or ship an asset, using the current metadata available in Cloudinary.

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

A ticket may describe an older version of an asset after metadata changes.

  • Reduce stale asset details in tickets.
  • Make current metadata easier to find during review.
  • Avoid repeated manual updates.

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 how to find Jira issues linked to Cloudinary assets and which available metadata should refresh their details.
  • 4Pick a recurring schedule and choose where run reports should go.
  • 5Run once on a real linked asset and issue to test.

Questions about this workflow

How are assets matched to Jira issues?

The workflow needs a reference, such as an asset URL or identifier in the Jira issue. If that link is absent, provide a reliable matching source.

Which metadata can be refreshed?

Only fields Cloudinary makes available and Jira can update. Name the fields in your instruction and avoid assuming unavailable history or baselines.

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.