Keep private issue changes connected to document context
A change to a private issue can prompt Notis to retrieve relevant parsed results, helping the team pick up the updated work with less searching.
Trigger
Private Team Issue Properties Updated
Fires when properties on an issue change in a private Linear team (polled with the connected user's token).
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
When private work changes direction or ownership, useful document context can remain out of sight and delay the next step.
- Revisits relevant parsed results when private issue details change.
- Helps a new owner or next step start with better document context.
- Reduces follow-up that depends on remembering where paperwork lives.
Setup
Build it in a few focused steps.
- 1Connect Linear and Docparser to Notis once through the portal, using an account with access to the private team.
- 2Create the automation in the portal or ask Notis in plain language.
- 3Ask Notis to retrieve Docparser results relevant to a private issue when its properties change, then summarize possible matches.
- 4Choose the Private Team Issue Properties Updated trigger and a channel for run reports.
- 5Test by updating a suitable real issue and checking the retrieved results.
Questions about this workflow
Does this trigger work for private teams?
Yes. It polls with the connected user's token, so the account must have access to the relevant team.
Will Notis decide which result is correct?
It can surface potentially relevant parsed results. Review the results to confirm which documents apply.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Linear to Docparser. A trigger fires from one place; an action lands in another.
Linear 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.
Comment Received Trigger
Triggered when a comment is received.
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.
Issue Created Trigger
Triggered when a new issue is created.
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.
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
Private Team Comment Created
Fires when a new comment is posted on an issue in a private Linear team (polled with the connected user's token).
Private Team Issue Created
Fires when a new issue appears in a private Linear team (polled with the connected user's token).
Private Team Issue Properties Updated
Fires when properties on an issue change in a private Linear team (polled with the connected user's token).
Connect any two apps with Notis in the middle.
Linear 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.