Skip to content
Notis

Keep Jira aligned with asset changes

When a meaningful asset update arrives, refresh the related Jira issue with the new supplied context.

Trigger

Webhook received

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

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

Ticket details can become stale after an asset is replaced or revised.

  • Keep ticket context current as work evolves.
  • Make asset revisions easier to spot.
  • Avoid hand editing issue details after each change.

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 to update the Jira issue key in each request with the changed Cloudinary asset details supplied there.
  • 4Pick the webhook trigger and choose where run reports should go.
  • 5Send one real asset change notification for an existing issue to test.

Questions about this workflow

Does this detect changes inside Cloudinary by itself?

No Cloudinary trigger event is listed. Your system must send an HTTP request to the Notis webhook when the change occurs.

Which Jira fields will be updated?

Describe the intended update in the automation instruction. Provide the target issue and the new values in the request or make them retrievable from Cloudinary.

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.