Put market risk context on the Jira issue
When a news development changes the risk around a project, update the issue with a clear summary that is easy to revisit.
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
Risk context can stay in someone's notes or inbox while the Jira issue continues to describe yesterday's assumptions.
- Keep risk context with the affected work
- Make changed assumptions visible to collaborators
- Reduce the chance of acting on stale issue details
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 to assess the submitted Benzinga development against the specified Jira issue and update the issue description with a concise, sourced risk note when relevant.
- 4Pick the webhook trigger and choose where run reports should go.
- 5Test with one real development and issue, then review the updated issue.
Questions about this workflow
Will the workflow overwrite the whole issue description?
The instruction should specify how to preserve existing context and where to add the risk note. Review the test update before relying on it.
Can Notis decide whether something is a risk?
It can assess the information you provide against your criteria. Supply your risk definitions and business context for a grounded assessment.
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.
Add Attachment
Uploads and attaches a file to a jira issue.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Add Comment
Adds a comment using atlassian document format (adf) for rich text to an existing jira issue.
Add Watcher to Issue
Adds a user to an issue's watcher list by account id.
Assign Issue
Assigns a jira issue to a user, default assignee, or unassigns; supports email/name lookup.
Bulk Create Issues
Creates multiple jira issues (up to 50 per call) with full feature support including markdown, assignee resolution, and priority handling.
Create Issue
Creates a new jira issue (e.g., bug, task, story) in a specified project.
Link Issues
Links two jira issues using a specified link type with optional comment.
Create Project
Creates a new jira project with required lead, template, and type configuration.
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.