Connect Adrapid to Docnify

When something happens in Adrapid, Notis takes the next step in Docnify. 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 Adrapid to Docnify

View example

Send an approved Adrapid campaign document for signature

When an Adrapid webhook supplies an approved campaign document with uploaded content, confirmed recipients, and an explicit send instruction, send it through Docnify.

View example

Resend a Docnify request after an Adrapid follow-up

Use an Adrapid webhook carrying a real campaign follow-up and confirmed Docnify document ID to resend a signing request.

View example

Inspect the Docnify document linked to an Adrapid asset

Fetch the current Docnify document state when an Adrapid webhook supplies a related document ID and asset context.

View example

List Docnify documents for an Adrapid campaign review

When Adrapid sends a real campaign export, list Docnify documents so a founder can review available signing packages.

View example

List Docnify templates for an Adrapid creative handoff

Use an Adrapid template or campaign export as context while listing available Docnify templates for selection.

View example

Inspect a Docnify template referenced by Adrapid

Fetch a confirmed Docnify template ID supplied alongside an Adrapid campaign or reusable-template export.

View example

Update Docnify fields from an approved Adrapid brief

Update existing Docnify field metadata when an Adrapid webhook supplies a confirmed document ID, field IDs, and approved changes.

View example

Add Docnify fields to an Adrapid approved document

Create fields only when an Adrapid webhook supplies a confirmed Docnify document ID, exact field specifications, and approval to prepare it for signing.

View example

Correct a Docnify recipient from an Adrapid approval update

Update a confirmed Docnify recipient when Adrapid sends an approved correction with document and recipient IDs plus exact replacement details.

Supported Triggers and Actions

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

Adrapid triggers

Docnify actions

Recurring trigger

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

TriggerScheduled

Add Document Recipient

Adds a recipient to a document.

ActionInstant

Webhook trigger

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

TriggerInstant

Create Document Fields

Adds fields to a document.

ActionInstant

Delete Document

Permanently deletes a document.

ActionInstant

Delete Document Field

Removes a field from a document.

ActionInstant

Delete document recipient

Removes a recipient from a document and revokes their access.

ActionInstant

Get Document

Retrieves a document’s current state and details.

ActionInstant

Get Template

Retrieves details about a template.

ActionInstant

List Documents

Lists documents in the account.

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.