Refresh parsed results when a Jira issue changes
Keep document data in view when the related Jira work changes, without repeatedly opening Docparser to fetch results.
Trigger
Updated Issue
Fires when an existing issue is changed in the Jira project you configure — for example its status, assignee, or any other field on the issue is updated. Only issues in that project produce an event. It does not fire on comment activity: adding, editing, or deleting a comment on an issue will not produce an event from this trigger.
Action
Get Multiple Document Results
Tool to retrieve parsed data from multiple documents processed by a specific parser. Use when you need to fetch results for multiple documents at once. Returns up to 100 results by default, with a maximum of 10000.
Why this helps
Updated ticket context can make teams re-check parsed documents manually and lose time finding the right results.
- Retrieve a batch of parsed results for review.
- Tie refreshed document data to a Jira issue change.
- Reduce repeated manual lookups in Docparser.
Setup
Build it in a few focused steps.
- 1Connect Jira and Docparser once in the Notis portal.
- 2Create an automation in Automations, New Automation, with a name and prompt.
- 3Tell Notis which parser's results to retrieve and how to summarize them for the changed issue.
- 4Pick the Jira Updated Issue trigger and choose where run reports go.
- 5Test with one real issue update and a parser ID supplied in context.
Questions about this workflow
How many results can the action return?
It returns up to 100 by default and supports a maximum of 10,000.
Do Jira comments trigger this workflow?
No. The Updated Issue event description excludes comment activity.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Docparser. A trigger fires from one place; an action lands in another.
Jira triggers
Docparser actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Multiple Document Results
Tool to retrieve parsed data from multiple documents processed by a specific parser. Use when you need to fetch results for multiple documents at once. Returns up to 100 results by default, with a maximum of 10000.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Parser Models
Tool to retrieve all model layouts for a specific parser. Use when you need to list different layout configurations within a parser that help handle document variations.
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
List Parsers
Tool to retrieve all Document Parsers linked to your account. Use when you need to view available parsers or obtain parser IDs for subsequent operations.
New Project
Triggered when a new project is added in Jira
Ping API
Tool to test API authentication and connection health check for Docparser API. Use when you need to verify that API credentials are valid and the connection is working.
Updated Issue
Fires when an existing issue is changed in the Jira project you configure — for example its status, assignee, or any other field on the issue is updated. Only issues in that project produce an event. It does not fire on comment activity: adding, editing, or deleting a comment on an issue will not produce an event from this trigger.
Connect any two apps with Notis in the middle.
Jira and Docparser, 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 Docparser.