Connect Outlook to Elasticsearch

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

View example

Find context for incoming Outlook email

Search a chosen Elasticsearch index for documents related to each new Outlook message and send a concise context report.

View example

Look up records for new calendar events

Search Elasticsearch for records related to a newly created Outlook event and prepare a compact meeting context report.

View example

Find existing records for a new Outlook contact

Search a chosen Elasticsearch index for documents mentioning a newly added Outlook contact and summarize possible matches.

View example

Check records after a calendar event changes

Search Elasticsearch after an Outlook event is created, updated, or deleted to find related records that may need attention.

View example

Check records related to sent Outlook messages

Search a chosen Elasticsearch index after you send a message to find related records for a lightweight follow-up review.

View example

Review your Elasticsearch index inventory

On a schedule, list Elasticsearch indices and send a compact inventory report for a quick workspace check.

View example

Inspect an Elasticsearch index schema on request

Send a webhook to have Notis retrieve the mapping for a specified index and report its fields and types.

View example

Check Elasticsearch connectivity on a schedule

Ping your Elasticsearch cluster on a recurring schedule and send a report confirming whether it responds.

Supported Triggers and Actions

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

Outlook triggers

Elasticsearch actions

Recurring trigger

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

TriggerScheduled

Get Index Schema

View the structure and field mappings of an index.

ActionInstant

Webhook trigger

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

TriggerInstant

List Indices

Lists available Elasticsearch indices.

ActionInstant

New Contact Added

Fires when a new contact is added to the contacts list.

TriggerInstant

Query Index

Searches an Elasticsearch index for documents.

ActionInstant

Calendar Event Changes

Fires when a calendar event is created, updated, or deleted.

TriggerInstant

Ping Cluster

Pings the cluster to check its connectivity and health.

ActionInstant

New Calendar Event

Fires when a new calendar event is created.

TriggerInstant

New Outlook Message

Fires when a new message arrives in the watched mail folder.

TriggerInstant

New Sent Message

Fires when a new message is sent from the watched mail folder.

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.