Organize claim evidence from each new ticket
Turn scattered document references into a clear claim evidence review.
Trigger
New Zendesk Ticket
Triggers when a new ticket is created in a specified Zendesk view.
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
Claims stall when reviewers must hunt through parsed documents before understanding the case.
- Reduce time spent locating claim evidence
- Present facts in a repeatable order
- Make missing documents visible immediately
Setup
Build it in a few focused steps.
- 1Connect Zendesk and Docparser in Notis.
- 2Create an automation and describe how to organize claim evidence in one plain-language instruction.
- 3Tell Notis to retrieve multiple results from the configured parser for document identifiers included in each claim ticket and group facts by evidence type.
- 4Pick the New Zendesk Ticket trigger and choose where reports should appear.
- 5Test with one real claim ticket.
Questions about this workflow
Can this handle more than one document?
Yes. It uses the action designed to retrieve multiple document results from one parser.
What evidence categories should I use?
Name the categories in your instruction, based on the review process you already use.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Zendesk to Docparser. A trigger fires from one place; an action lands in another.
Zendesk 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 User Created
Triggered when a new user is created in Zendesk.
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 Zendesk Ticket
Triggers when a new ticket is created in a specified Zendesk view.
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.
Connect any two apps with Notis in the middle.
Zendesk 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.