Connect ActiveMerge to Docnify

When something happens in ActiveMerge, 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 ActiveMerge to Docnify

View example

Check an ActiveMerge document before signing

When an ActiveMerge document is ready for review, fetch its Docnify record so you can confirm its current state and metadata before asking anyone to sign.

View example

Add the right signer to a Docnify document

Use an ActiveMerge handoff to add a recipient to a confirmed Docnify document, with signing order or authentication options when supplied.

View example

Prepare Docnify fields for a generated document

After ActiveMerge hands off a document ID, fetch its Docnify record and create the requested signing fields before the document is sent.

View example

Update Docnify field requirements before sending

When a handoff identifies a Docnify document and existing fields, update their labels or requirements before the document is sent.

View example

Correct a Docnify signer from a handoff

Update a signer's supplied name, email, or role on a Docnify document after confirming its document and recipient IDs.

View example

Revoke a recipient's Docnify access

When an authorized handoff identifies a Docnify document and recipient to remove, verify both IDs and remove that recipient.

View example

Resend a verified Docnify signing request

Use a clear ActiveMerge follow-up handoff to resend a Docnify document for signing after confirming its ID.

View example

Review Docnify documents on a schedule

On a schedule, list Docnify documents and have Notis summarize the returned records so you can spot signing work that needs attention.

View example

Keep a scheduled Docnify template inventory

On a recurring schedule, list Docnify templates and receive a concise inventory of the templates available for document workflows.

Supported Triggers and Actions

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

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