Connect Outlook to Docnify
When something happens in Outlook, 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
Ways Notis can move work from Outlook to Docnify
Turn Outlook signature requests into a Docnify document queue
When a new Outlook message asks for a signature, review Docnify documents and report the matching document and current status.
Check Docnify signing status from incoming Outlook mail
When a new Outlook message mentions a document, fetch its Docnify record and summarize recipients, status, and next action.
Send a prepared Docnify document after a calendar meeting
After a new Outlook calendar event, send the confirmed Docnify document for signing when the meeting instructions identify it and the recipients.
Resend Docnify requests when Outlook calendar timing changes
When an Outlook calendar event changes, review the related Docnify document and resend the signing request if the new timing makes a reminder useful.
Update a Docnify signer after sending corrected Outlook details
When a sent Outlook message contains corrected signer information, update the matching Docnify recipient after confirming the document and recipient IDs.
Add a Docnify recipient from a clear Outlook signing request
When a new Outlook message names an additional signer, add that recipient to the confirmed Docnify document with the requested order and authentication details.
Remove a revoked Docnify signer after an Outlook notice
When an Outlook message confirms that a signer should be removed, delete that recipient from the specified Docnify document after verifying both IDs.
Check Docnify documents when a new Outlook contact is added
When a new Outlook contact is added, list Docnify documents and report any active documents that may need this contact as a signer.
Review Docnify templates before a new Outlook meeting
When a new Outlook calendar event is created, list Docnify templates and report which one best fits the meeting context for manual confirmation.
Supported Triggers and Actions
Notis builds workflows that link Outlook to Docnify. A trigger fires from one place; an action lands in another.
Outlook triggers
Docnify actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add Document Recipient
Tool to add a recipient to a document. Use after confirming the document's ID. Optionally specify signing order and authentication options.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Document Fields
Tool to create one or more fields on a document. Use after fetching a document to add fields before sending.
New Contact Added
Triggered when a new contact is added in the Outlook contacts.
Delete Document
Tool to delete a specific document by its ID. Use when you have confirmed the document should be permanently removed.
Calendar Event Changes
Triggered when a new calendar event occurs (created, updated, or deleted) in the Outlook calendar.
Delete Document Field
Tool to delete a field from a document. Use when you need to remove a specific field from an existing document.
New Calendar Event
Triggered when a new calendar event is created in the Outlook calendar.
Delete document recipient
Tool to remove a recipient from a document. Use after verifying document and recipient IDs to revoke access.
New Outlook Message
Triggered when a new message is received in the Outlook mailbox.
Get Document
Tool to fetch a specific document by its ID. Use when you need to view a document's current state and metadata.
New Sent Message
Triggered when a new message is sent from the Outlook mailbox.
Get Template
Tool to fetch a specific template by its ID. Use to view a template's details and metadata.
List Documents
Tool to list documents in the Docnify account.
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.
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.
Recurring triggers
Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.
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.
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.
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:
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
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.
More ways to connect Outlook and Docnify
Connect any two apps with Notis in the middle.
Outlook and Docnify, or any other combination from 1,000+ 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.