Connect Outlook to Addresszen

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

View example

Check Addresszen key for inbound address requests

When a new Outlook message asks for address help, confirm the Addresszen key is available before any lookup.

View example

Resolve a shipping address ID from an inbound email

When an Outlook email includes an Addresszen suggestion ID, resolve it into a complete US address for delivery work.

View example

Resolve an address before sending delivery confirmation

When a sent Outlook message includes an Addresszen suggestion ID, resolve it and keep the verified address in the run report.

View example

Resolve a new contact shipping address

When a new Outlook contact includes an Addresszen suggestion ID, resolve the contact's complete US address.

View example

Resolve a venue address from a new calendar event

When a new Outlook calendar event contains an Addresszen suggestion ID, resolve the venue into a full US address.

View example

Recheck an address after a calendar change

When an Outlook calendar event changes and carries an Addresszen suggestion ID, resolve the current address again.

View example

Check Addresszen access before customer location review

When a customer location review arrives by Outlook, verify the Addresszen key before the team starts work.

View example

Check Addresszen key after a location related send

When a location related Outlook message is sent, confirm the Addresszen key remains available for follow-up work.

View example

Check Addresszen key from a support webhook

Start from an HTTP request when support flags an address issue, then verify Addresszen key availability.

Supported Triggers and Actions

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

Outlook triggers

Addresszen actions

Recurring trigger

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

TriggerScheduled

Key Availability

Tool to get public information on an api key, including whether it is currently usable. use when you need to verify that a key is valid and available before making further api requests.

ActionInstant

Webhook trigger

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

TriggerInstant

Resolve Address USA

Tool to resolve an address autocompletion by its address id and return the full address in us format. use after obtaining an address suggestion id from the autocomplete endpoint.

ActionInstant

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.