Connect Outlook to Docupilot

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

View example

Create a Docupilot folder for every new Outlook contact

When a contact is added in Outlook, create a clearly named Docupilot folder for their relationship records.

View example

Create a Docupilot folder for each new Outlook meeting

When a calendar event is created, prepare a Docupilot folder for its notes, briefs, and follow-up documents.

View example

Check Docupilot folders when an Outlook event changes

When a calendar event is created, updated, or deleted, list Docupilot folders so Notis can identify the relevant workspace context.

View example

Confirm the Docupilot account for new Outlook messages

When a new Outlook message arrives, retrieve the authenticated Docupilot user so Notis can confirm the correct workspace before document work.

View example

Create a Docupilot folder for sent contract follow-ups

After a contract related message is sent from Outlook, create a Docupilot folder for the follow-up record.

View example

Review Docupilot folders for incoming document requests

When a new Outlook message requests a document, list Docupilot folders so Notis can identify the best existing workspace.

View example

Create a Docupilot project folder from a new Outlook event

When a project kickoff or delivery event is added, create a dedicated Docupilot folder for its project record.

View example

Confirm Docupilot identity after a new Outlook contact

When a new contact is added, retrieve the authenticated Docupilot user before Notis begins relationship document organization.

Supported Triggers and Actions

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

Outlook triggers

Docupilot actions

Recurring trigger

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

TriggerScheduled

Create Docupilot Folder

Tool to create a new folder. use when organizing documents into custom workspace folders after confirming workspace context.

ActionInstant

Webhook trigger

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

TriggerInstant

Create Docupilot Folder

Tool to create a new folder. use when organizing documents into custom workspace folders after confirming workspace context.

ActionInstant

New Contact Added

Triggered when a new contact is added in the Outlook contacts.

TriggerInstant

List all folders

Tool to list all folders. use after authentication to fetch available workspace folders.

ActionInstant

Calendar Event Changes

Triggered when a new calendar event occurs (created, updated, or deleted) in the Outlook calendar.

TriggerInstant

Get Authenticated User

Tool to retrieve information about the authenticated user. use after authentication to confirm identity and fetch user account details.

ActionInstant

New Calendar Event

Triggered when a new calendar event is created in the Outlook calendar.

TriggerInstant

New Outlook Message

Triggered when a new message is received in the Outlook mailbox.

TriggerInstant

New Sent Message

Triggered when a new message is sent from the Outlook mailbox.

TriggerInstant

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.