Connect Outlook to Aivoov

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

View example

Match incoming voiceover requests to available Aivoov voices

When a new Outlook message requests a voiceover, retrieve Aivoov voices that fit the requested language and style.

View example

Prepare narration voices for new calendar events

When a new Outlook calendar event is created, list Aivoov voices suited to the event title, audience, and language you specify.

View example

Refresh voice options when an Outlook event changes

When an Outlook calendar event is updated or deleted, retrieve a refreshed Aivoov voice list for the remaining production work.

View example

Turn a sent Outlook brief into Aivoov voice options

After you send a production brief, list Aivoov voices that match its language, audience, and delivery direction.

View example

Find a welcome voice when a new contact is added

When a new Outlook contact is added, list Aivoov voices for a personalized welcome or onboarding message based on the contact context you provide.

View example

Check submitted voice criteria against Aivoov

When a Notis webhook receives a voice request, list Aivoov voices that satisfy the submitted language and delivery criteria.

View example

Review Aivoov voice availability on a schedule

On a recurring Notis schedule, retrieve Aivoov voices for the languages and styles your upcoming Outlook work commonly needs.

View example

Create a fast voice shortlist for urgent Outlook requests

When an urgent request arrives in Outlook, identify its constraints and return a concise Aivoov voice shortlist for rapid approval.

Supported Triggers and Actions

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

Outlook triggers

Aivoov actions

Recurring trigger

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

TriggerScheduled

List Voices

Tool to retrieve a list of available voices. use to filter voices by language after confirming api key is valid.

ActionInstant

Webhook trigger

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

TriggerInstant

New Contact Added

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

TriggerInstant

Calendar Event Changes

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

TriggerInstant

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.