Skip to content
Notis

Keep Jira documentation current when a playlist disappears

If a Jira issue refers to a playlist that no longer exists, update the record so nobody follows a dead reference.

Trigger

New Playlist Created or Deleted

Triggers when a new playlist is created or deleted.

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 deleted playlist can leave Jira instructions or project notes pointing people to something they cannot access.

  • Keep an existing Jira record current after playlist deletion.
  • Reduce confusion from references to unavailable playlists.
  • Make the cleanup visible alongside the related work.

Setup

Build it in a few focused steps.

  • 1Connect Spotify and Jira once in the Notis portal.
  • 2Create an automation in Automations, New Automation, and give it a name.
  • 3Describe which existing Jira issue to update when the named playlist is deleted, including the replacement or cleanup note if known.
  • 4Pick New Playlist Created or Deleted as the trigger and choose where run reports should go.
  • 5Test with one real deletion event if available, or review the prompt against a representative event.

Questions about this workflow

Does this find all Jira issues that mention the playlist?

No. Specify the Jira issue to update in your instruction. The listed actions do not provide a broad text search and update sequence as one action.

Can it add a replacement playlist link?

Yes, if you provide the replacement link in the instruction or otherwise make it available to Notis. The deletion event may not include a replacement.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

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

Spotify 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

New Device Added

Triggers when a new device is added.

TriggerPolling

Add Watcher to Issue

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

ActionInstant

Spotify Playlist Item Change

Triggers when songs are added to or removed from a Spotify playlist.

TriggerPolling

Assign Issue

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

ActionInstant

New Playlist Created or Deleted

Triggers when a new playlist is created or deleted.

TriggerPolling

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.

Spotify 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.