Connect Outlook to Elorus
When something happens in Outlook, Notis takes the next step in Elorus. 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 Elorus
Draft an Elorus invoice from a client email
Turn a client email with clear billing details into an Elorus invoice, and flag missing information for review.
Find the Elorus contact behind a new email
Use an incoming Outlook message to look up Elorus contacts and report likely matches for follow-up.
Prepare an invoice list for upcoming client meetings
When a new Outlook calendar event is created, retrieve Elorus invoices so you can review billing before the meeting.
Refresh invoice review when a meeting changes
When an Outlook calendar event changes, retrieve relevant Elorus invoices so your billing context stays aligned with the meeting.
Check whether a new Outlook contact is in Elorus
When Outlook gets a new contact, retrieve Elorus contacts and report whether a likely billing record already exists.
Review client invoices after sending an email
After an Outlook message is sent, retrieve relevant Elorus invoices to support the next billing follow-up.
Retrieve Elorus expenses for a review request
Start a review from a Notis webhook and retrieve a page of Elorus expenses for a specified review period or criteria.
Run a recurring Elorus invoice review
On a schedule, retrieve Elorus invoices using the criteria you specify and send a concise review to your chosen report channel.
Look up Elorus bills when a request arrives
Use a webhook request to retrieve Elorus bills that match supplied criteria and report the results for review.
Supported Triggers and Actions
Notis builds workflows that link Outlook to Elorus. A trigger fires from one place; an action lands in another.
Outlook triggers
Elorus actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Invoice
Create an invoice or receipt, saved as a draft by default.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Expense
Creates an expense from categorized line items.
New Contact Added
Fires when a new contact is added to the contacts list.
CREATE_PRODUCT
Create a product or service in the catalog.
Calendar Event Changes
Fires when a calendar event is created, updated, or deleted.
Email Invoice
Email an existing invoice to selected contacts.
New Calendar Event
Fires when a new calendar event is created.
Get Bills
Retrieve bills for viewing and managing expenses or purchases.
New Outlook Message
Fires when a new message arrives in the watched mail folder.
Delete Invoice
Permanently deletes a draft invoice; issued invoices cannot be deleted.
New Sent Message
Fires when a new message is sent from the watched mail folder.
Get Contacts
Retrieve your contacts.
Get Credit Notes
Retrieve credit notes.
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 Elorus
Connect any two apps with Notis in the middle.
Outlook and Elorus, 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 Elorus.