Skip to content
Notis

Find the right parser for a compliance evidence request

Start with an inventory of your available parsers, then use the relevant parser in a focused evidence review.

Trigger

Webhook received

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

Action

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.

Why this helps

When parser names and purposes are hard to recall, choosing where to look can delay an audit evidence review.

  • Retrieve the account's available Docparser parsers on request.
  • Make parser discovery part of a compliance review workflow.
  • Avoid searching manually when a new evidence request arrives.

Setup

Build it in a few focused steps.

  • 1Connect 21risk and Docparser once in the Notis portal.
  • 2Create an automation in Automations, New Automation, and give it a name.
  • 3In one instruction, ask Notis to list the available Docparser parsers and summarize which appear relevant to the evidence request and its 21risk context.
  • 4Choose the webhook trigger and where run reports should go.
  • 5Test with one real evidence request and confirm the parser inventory is clear.

Questions about this workflow

Does this workflow choose a parser automatically?

It lists the parsers linked to your account. Notis can help interpret the inventory against the request, but parser relevance depends on the available names and context.

Does this retrieve document results too?

No. This workflow uses the List Parsers action. A separate workflow using Get Multiple Document Results can retrieve parsed data.

What starts the inventory lookup?

An HTTP request to the Notis webhook starts it.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

Notis builds workflows that link 21risk to Docparser. A trigger fires from one place; an action lands in another.

21risk triggers

Docparser actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

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.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

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.

ActionInstant

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.

ActionInstant

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.

ActionInstant

Connect any two apps with Notis in the middle.

21risk 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.