Connect Abyssale to DocRaptor

When something happens in Abyssale, Notis takes the next step in DocRaptor. Describe what you want in plain English, or start from one of the examples below.

When this happens · Trigger

Do this · Action

Build an automation Browse examples

Examples

Ways Notis can move work from Abyssale to DocRaptor

View example

Turn a finished campaign creative into a review PDF

When Abyssale sends a completed creative to a Notis webhook, create a clean PDF proof with the asset, campaign details, and review notes included in the request.

View example

Build a batch creative review packet

Use an incoming batch request to create an asynchronous PDF packet from multiple Abyssale creative entries, useful when a campaign needs one review bundle.

View example

Create a usage guide for an approved creative

When an approved Abyssale asset is submitted through a webhook, turn its supplied usage details into a concise PDF guide for the people using it.

View example

Make a delivery spec sheet for a creative video

Create a PDF sheet from an Abyssale video delivery request, keeping supplied format, dimensions, destinations, and deadlines together for handoff.

View example

Turn an Abyssale template list into a catalog

Submit a template list and its supplied descriptions to a webhook to create a browsable PDF catalog for internal selection and reuse.

View example

Prepare a weekly creative roundup

On a schedule, create a PDF roundup from the Abyssale creative updates or asset list supplied to the automation, with highlights and links included when available.

View example

Create a monthly asset inventory report

Generate an asynchronous monthly PDF inventory from an Abyssale asset list made available to Notis, keeping supplied names, types, and links in one report.

View example

Create a campaign creative handoff brief

Turn a campaign handoff request into a PDF brief with supplied Abyssale assets, creative intent, deadlines, and next steps together.

View example

Keep a PDF record of a creative approval

When a creative approval is submitted through a webhook, produce a dated PDF record using the approval details, asset reference, and notes in the request.

Supported Triggers and Actions

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

Abyssale triggers

DocRaptor actions

Recurring trigger

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

TriggerScheduled

Create Async Document

Creates a document asynchronously from HTML content.

ActionInstant

Webhook trigger

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

TriggerInstant

Create Document

Creates a PDF or Excel document from HTML content or a URL and returns it immediately.

ActionInstant

Create Document from Referrer

Converts webpages into PDF or Excel documents.

ActionInstant

Create Hosted Async Document

Creates a hosted document asynchronously.

ActionInstant

Download Async Document

Downloads a completed asynchronous document.

ActionInstant

Get Async Document Status

Checks the progress of asynchronous document creation.

ActionInstant

List Documents (JSON)

Lists previously created documents with metadata in JSON format.

ActionInstant

List Documents (XML)

Lists previously created documents with metadata in XML format.

ActionInstant

Trigger Types

Four ways to start an automation.

A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a recurring schedule, and soon, your own database.

Integration triggers

Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,000+ apps can start a workflow.

New Notion pageStripe chargeCalendar event

Webhook triggers

A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.

Any HTTP POSTCustom backendIoT event

Works with

ZapierPipedream

Most used

Recurring triggers

Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.

Daily · 8:00HourlyWeekdays only

Coming soon

Database triggers

Watch a row, query, or threshold in your own database and fire the moment the data changes. Row inserted, value crosses a limit, query starts matching.

Row insertedValue > limitQuery match

Why AI automation

Classic automation breaks. AI adapts.

Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.

Classic automationAI automation

Cost

$ · pay per run

$$ · AI models per run

Reliability

Breaks on schema change

Adapts to format changes

Setup

Click 8 dropdowns

Describe it in English

Handles fuzzy

Hard-coded fields only

Reads intent, summarises

Human in loop

Bolted on

Built in · approval inbox

Maintenance

You own every break

Self-heals · we own it

Ease of use

Describe it. Notis builds it.

Skip the visual builder. Tell Notis what you want, in plain English. It writes the workflow, you review and deploy.

You · in the Notis Builder

NEW

“When a row gets added to the Q4 OKRs Notion database and the status is Blocked, send a Telegram message to the owner with a summary of what's blocking, and ping me if there's no reply within 24 hours.”

Notis built this automation:

TriggerRow added to "Q4 OKRs"

Condition✦Status = "Blocked"

AI step✦Summarise the blocker in plain English

ActionDM the row owner with summary

Timeout✦No reply in 24h → ping you

Observability

Watch every run.

Notis Desktop is Mission Control for your AI automations. See every run, replay, edit, or rewind. Set approval gates so Notis pauses before destructive actions.