Send a contract when its Notion record is ready
When a new contract record appears in the chosen Notion database, have Notis identify its matching prepared Docnify document and send it to the intended signer.
Connect Notion to Docnify
When something happens in Notion, 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
Fires when a new comment is created in the accessible workspace.
Do this · Action
Adds a recipient to a document.
Examples
Ways Notis can move work from Notion to Docnify
Keep Docnify signer details current
When signer details change on a Notion record, have Notis locate the matching Docnify recipient and update the relevant contact information.
Resend a signing request when follow-up is due
When a Notion signing record is updated to indicate a follow-up is due, have Notis verify the matching Docnify document and resend its signing request.
Send an agreement after a Notion approval comment
When a new comment on an agreement page clearly records approval to send, have Notis identify the prepared Docnify document and send it for signature.
Adjust Docnify fields after agreement edits
When agreement page content changes, have Notis review the described signing-field requirements and update existing Docnify field metadata before sending.
Start client paperwork from a new onboarding page
When a client onboarding page is created in Notion, have Notis find the prepared Docnify agreement and send it to the client signer.
Add an investor signer to the confirmed document
When an investor record changes to indicate an additional signer, have Notis confirm the relevant Docnify document and add that recipient.
Refresh field guidance for a new signing checklist
When a new Notion checklist page is added, have Notis use its requirements to update metadata on existing fields of the corresponding Docnify document.
Correct a signer role on the live request
When a Notion page block is updated with a corrected signer role, have Notis locate the corresponding Docnify recipient and update that role.
Supported Triggers and Actions
Notis builds workflows that link Notion to Docnify. A trigger fires from one place; an action lands in another.
Notion 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
Comment Created
Fires when a new comment is created in the accessible workspace.
TriggerInstant
Delete Document
Permanently deletes a document.
ActionInstant
Database Created
Fires when a new database container is created.
TriggerInstant
Delete Document Field
Deletes a specific field from a document; the response may not reveal API errors.
ActionInstant
Data Source Created
Fires when a new data source is created in the workspace.
TriggerInstant
Delete document recipient
Removes a recipient from a document and revokes their access.
ActionInstant
Data Source Schema Updated
Fires when a data source’s columns are added, removed, or renamed.
TriggerInstant
Get Document
Fetches a document by ID; the result may contain an API error instead of the document.
ActionInstant
Page Content Updated
Fires when the body content of an accessible page is updated.
TriggerInstant
Get Template
Fetches a template by ID; the result may contain an API error instead of the template.
ActionInstant
Page Created
Fires when a new page is created in the accessible workspace.
TriggerInstant
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 schedule (recurring or one-time), and a change in one of your Notis databases.
Integration triggers
Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,500+ 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
Scheduled triggers
Run a workflow on the clock, on a recurring schedule or once at a set date and time. Daily standups, hourly syncs, a one-off launch reminder: the workhorse of Notis.
Daily · 8:00Weekdays onlyOnce · Dec 13
Beta
Database triggers
Fire when a row in one of your Notis databases is added or edited, with optional filters on its properties. New lead added, status changed, value crosses a limit.
Row addedProperty editedValue > limit
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.
- Full run history with inputs, outputs and traces
- Replay any run with edited inputs
- Approval inbox, confirm via chat in one tap
- Audit logs for compliance teams
Automations
Inbox
All12Manager5Telegram1Messages0WhatsApp2Email4Slack8
Migrate background jobs to a durable queue You can cancel it through Stripe
3 daysNotis v3 release update This one’s v3: Notis Manager (desktop app with …
8 daysAdd multi-tenant RBAC User initiates a voice call
13 daysDraft pricing v (tiers, limits, overages) and sanity-check margins
2 weeksVerify analytics events for new features That’s a really interesting automat…
1 monthEverything in the box.
Whatever starts the workflow, the platform underneath is the same: a thinking brain, full visibility, and you in control.
AI in the middle
Every step can include an LLM call: summarise, classify, extract, rewrite.
Full observability
Every run, every step, every input, all replay-able from Mission Control.
Human in the loop
Pause for approval. Notis pings you in chat with one-tap approve.
Self-healing
When an API changes shape, Notis adapts the parser. Less midnight fire-fighting.
Related pairs
More ways to connect Notion and Docnify
Connect any two apps with Notis in the middle.
Notion and Docnify, or any other combination from 1,500+ 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 Docnify.