Keep expense issues grounded in parsed receipt results
When an expense issue changes, Notis can look up related parsed receipts and surface useful details for the next decision.
Trigger
Issue Updated Trigger
Triggered when an issue is updated. For example labels are changed, issue status is changed, etc.
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
Expense work can lose momentum when an issue changes but its receipt evidence is still buried in a separate document workflow.
- Brings parsed receipt context back into view after an issue changes.
- Makes review easier when ownership, status, or other issue details are updated.
- Reduces the need to remember to revisit the document source.
Setup
Build it in a few focused steps.
- 1Connect Linear and Docparser to Notis once through the portal.
- 2Create an automation in the portal or ask Notis in plain language.
- 3Tell Notis to retrieve potentially related parsed receipt results when an expense issue changes and summarize relevant details.
- 4Choose the Linear Issue Updated trigger and a channel for run reports.
- 5Test by updating one real expense issue and reviewing the lookup.
Questions about this workflow
Will every issue update retrieve receipts?
The workflow runs on the selected Linear update event. Describe in the prompt which expense updates should receive a receipt lookup.
Does it edit the issue?
The described Docparser action retrieves parsed results. Issue edits are not part of this workflow.
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.