Keep account details current in Jira
Refresh the account context on a Jira ticket from a company lookup, without manually copying information between tools.
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
Account details can become stale in Jira while current company research sits elsewhere.
- Update a designated Jira issue after a company lookup.
- Use only details returned by BlitzAPI and relevant to the ticket.
- Reduce manual copying during account reviews.
Setup
Build it in a few focused steps.
- 1Connect BlitzAPI and Jira once in Notis.
- 2Create an automation and describe which company details should update the Jira issue.
- 3Pick the Notis webhook trigger.
- 4Choose where run reports should go.
- 5Test with one real company and a Jira issue intended for the update.
Questions about this workflow
What identifies the ticket to update?
Include its Jira key or identifier in the webhook request, or explain how the automation should identify it.
Can it fill in details BlitzAPI does not return?
No. Supply any missing account context yourself, or leave those details out of the update.
Can the update replace the ticket summary?
The Jira Edit Issue action supports direct fields such as summary and description. Specify precisely which fields to update in your instruction.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Blitz API to Jira. A trigger fires from one place; an action lands in another.
Blitz API 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.
Blitz API 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.