Skip to content
Notis

Let relevant market news move work to its next state

When a market development changes what should happen next, have Notis transition the related Jira issue using your workflow criteria.

Trigger

Webhook received

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

Action

Transition Issue

Transitions a jira issue to a different workflow state, with support for transition name lookup and user assignment by email.

Why this helps

A team may agree that news changes the next step but leave the issue in its old state, obscuring the real status of the work.

  • Keep issue status aligned with a defined response
  • Reduce manual status maintenance after a news review
  • Make the reasoning for a state change visible

Setup

Build it in a few focused steps.

  • 1Connect Benzinga and Jira once in the Notis portal.
  • 2Create an automation in Automations, New Automation, and give it a clear name.
  • 3Tell Notis what news criteria warrant a transition, which issue to evaluate, and the appropriate transition name when those criteria are met.
  • 4Pick the webhook trigger and choose where run reports should go.
  • 5Test with one real news item and Jira issue, then review the transition.

Questions about this workflow

Can Notis transition to any status?

Jira provides the available transitions for an issue. The requested transition must be available in that issue's workflow.

What happens when the criteria are not met?

Tell Notis to leave the issue unchanged unless the submitted news clearly meets your stated transition criteria.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

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

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

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