Connect Agile CRM to Docnify

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

View example

Add an Agile CRM Deal Contact as a Signer

When a deal is ready for paperwork, use its webhook payload and Agile CRM contact details to add the intended signer to a confirmed Docnify document.

View example

Update a Docnify Signer from Agile CRM

When a CRM correction arrives by webhook, verify the document and recipient, then update the signer's name, email, or role in Docnify.

View example

Resend a Docnify Signature Request After CRM Follow-up

After a follow-up decision in Agile CRM, send a webhook to Notis to resend a verified Docnify document for signing.

View example

Review Docnify Documents on a Schedule

Run a scheduled review of Docnify documents and use available Agile CRM context to highlight signing items that need a founder's attention.

View example

Check a Docnify Document Before CRM Follow-up

On a schedule, fetch a specified Docnify document and report its current state alongside the related Agile CRM contact or deal context.

View example

Remove a Docnify Recipient After a CRM Handoff Change

When a verified handoff change arrives by webhook, remove the specified recipient from the confirmed Docnify document to revoke their access.

View example

Remove an Obsolete Docnify Field After a CRM Correction

When a verified CRM correction makes a specific document field obsolete, remove that field from the confirmed Docnify document.

View example

Update Docnify Field Requirements After a CRM Correction

When a verified CRM correction changes signing requirements, update metadata on the specified existing Docnify fields before sending.

View example

Check a Docnify Template During Deal Preparation

When a deal reaches a preparation handoff, fetch the specified Docnify template and summarize its metadata with relevant Agile CRM context.

Supported Triggers and Actions

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

Agile CRM 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.