Connect Outlook to Brex
When something happens in Outlook, Notis takes the next step in Brex. 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 Brex
Review Brex expenses when a new Outlook email arrives
Use incoming Outlook messages to pull matching Brex expenses and prepare a focused review.
Find Brex transactions mentioned in Outlook emails
Search Brex transactions by description when a new Outlook message references a purchase or vendor.
Create a Brex budget for every new Outlook project event
When a project kickoff lands on your Outlook calendar, create the related Brex budget from the event context.
Create a Brex card for a new travel event
Use new Outlook travel events to create a dedicated Brex card for approved trip spending.
Update a Brex budget when an Outlook event changes
Use calendar changes to keep a related Brex budget aligned with revised project dates or scope.
Log a Brex expense after sending a purchase confirmation
Create a Brex expense from a sent Outlook message that confirms a purchase or reimbursement.
Check Brex transactions by amount from Outlook requests
When an email includes a disputed amount, search Brex transactions in that amount range and summarize candidates.
Retrieve a Brex transaction from an Outlook reference
Use a transaction ID in a new Outlook message to fetch the complete Brex transaction details.
Create a Brex user when a new Outlook contact is added
Turn a qualifying new Outlook contact into a Brex user record with the details available in the contact.
Supported Triggers and Actions
Notis builds workflows that link Outlook to Brex. A trigger fires from one place; an action lands in another.
Outlook triggers
Brex actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Budget
Create a new budget for departments or projects.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Card
Create a new card and assign it to a user.
New Contact Added
Triggered when a new contact is added in the Outlook contacts.
Create Department
Create a new department.
Calendar Event Changes
Triggered when a new calendar event occurs (created, updated, or deleted) in the Outlook calendar.
Create Expense
Create a new expense.
New Calendar Event
Triggered when a new calendar event is created in the Outlook calendar.
Create Location
Create a new location.
New Outlook Message
Triggered when a new message is received in the Outlook mailbox.
Create Job Title
Create a new job title.
New Sent Message
Triggered when a new message is sent from the Outlook mailbox.
Create User
Create a new user in the brex account.
Create Vendor Card
Create a new vendor card.
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 Brex
Connect any two apps with Notis in the middle.
Outlook and Brex, 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 Brex.