Skip to content
Notis

Find the parser that may hold your incident documents

See your available Docparser parsers in the context of an incoming abuse signal, then decide which one to use for a deeper review.

Trigger

Webhook received

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

Action

List Parsers

Lists document parsers linked to the account.

Why this helps

When parser names are unfamiliar, finding the right place for security evidence can interrupt an otherwise quick alert review.

  • See available parser names and identifiers in one run.
  • Use the alert context to focus attention on likely relevant parsers.
  • Make it easier to choose a parser for a later document review.

Setup

Build it in a few focused steps.

  • 1Connect Abuselpdb and Docparser once in the Notis portal.
  • 2Create an automation from Automations, New Automation, or tell Notis in plain language.
  • 3Ask Notis in one instruction to list Docparser parsers and point out names that may relate to the incoming abuse alert.
  • 4Pick the notis_webhook trigger and choose where run reports go.
  • 5Test with one real webhook and confirm the parser list helps you choose a relevant parser.

Questions about this workflow

Can this action search inside parsed document contents?

No. List Parsers returns parsers linked to your account. It does not retrieve document results or inspect their contents.

Can Notis know what every parser is for?

Notis can use the available parser information and webhook context to suggest a likely match. Add naming conventions or other context in your instruction if parser names are not descriptive.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

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

Abuselpdb 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

Retrieves parsed data from multiple documents.

ActionInstant

Webhook trigger

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

TriggerInstant

Get Parser Models

Lists layout models for a parser.

ActionInstant

List Parsers

Lists document parsers linked to the account.

ActionInstant

Ping API

Checks authentication and connection health.

ActionInstant

Connect any two apps with Notis in the middle.

Abuselpdb 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.