Skip to content
Notis

Create competitor ad briefs with the documents that matter

Send a competitor ad report to Notis and get a concise brief with relevant parsed document context and any missing evidence called out.

Trigger

Webhook received

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

Action

Get Multiple Document Results

Retrieves parsed data from multiple documents.

Why this helps

Competitor research and supporting documents live in separate places, making it easy to miss context or spend time assembling a brief by hand.

  • Combines an Adyntel report with relevant Docparser results in one brief.
  • Highlights missing or conflicting context for follow-up.
  • Reduces manual switching between ad research and document records.

Setup

Build it in a few focused steps.

  • 1Connect Adyntel and Docparser once in the Notis portal.
  • 2Create an automation in Automations, New Automation, and give it a name and prompt.
  • 3Tell Notis to use the submitted Adyntel competitor report, retrieve relevant results from the specified Docparser parser, and summarize the findings and gaps.
  • 4Choose the notis_webhook trigger and where run reports should go.
  • 5Test with one real competitor report and a parser that contains relevant documents.

Questions about this workflow

What starts this automation?

A webhook request starts it. Send the Adyntel competitor report and identify the Docparser parser to query in your instruction or request.

Does Docparser search every parser automatically?

The results action retrieves documents for a specific parser. Provide the parser identity in your instruction or request.

Can it confirm claims in the ad report?

Notis can compare the returned document results with the report and call out support, conflicts, or missing evidence. It cannot infer information absent from those inputs.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

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

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

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