Connect Outlook to Bolna
When something happens in Outlook, Notis takes the next step in Bolna. 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 Bolna
Call new Outlook leads with Bolna
Automatically call a promising new email lead with the right Bolna voice agent.
Schedule Bolna calls from new calendar events
Use a newly created Outlook event to schedule a Bolna calling batch for attendees or invitees.
Review Bolna execution status after calendar changes
When an Outlook event changes, check the related Bolna agent executions and report what needs attention.
Set up inbound Bolna coverage from a new Outlook message
When a new message requests phone support, configure the appropriate Bolna agent for inbound calls.
Audit Bolna agents when a new Outlook contact arrives
Review your Bolna agent roster when a new Outlook contact is added and report the best match.
Review Bolna follow-up execution after sending an Outlook message
After you send an Outlook message, retrieve detailed Bolna execution information for the related follow-up.
Check Bolna phone capacity for new Outlook requests
When a new message requests calling, list available Bolna phone numbers before you commit to follow-up.
Run a daily Bolna execution review
On a schedule, review agent executions and send a concise exception report for follow-up.
Review Bolna batch executions weekly
Run a weekly review of batch executions and summarize completion gaps or follow-up needs.
Supported Triggers and Actions
Notis builds workflows that link Outlook to Bolna. A trigger fires from one place; an action lands in another.
Outlook triggers
Bolna actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Delete agent by id
Delete an agent
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete batch by id
Delete a batch
New Contact Added
Triggered when a new contact is added in the Outlook contacts.
Fetch all batches by agent id
List all batches for agent
Calendar Event Changes
Triggered when a new calendar event occurs (created, updated, or deleted) in the Outlook calendar.
Get all agents
List all agents
New Calendar Event
Triggered when a new calendar event is created in the Outlook calendar.
Get all phone numbers
List all phone numbers for your account
New Outlook Message
Triggered when a new message is received in the Outlook mailbox.
Get execution by id
Retrieve specific execution by `execution id`
New Sent Message
Triggered when a new message is sent from the Outlook mailbox.
Make a phone call from agent
Initiate calls
Retrieve agent by id
Retrieve an agent
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 Bolna
Connect any two apps with Notis in the middle.
Outlook and Bolna, 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 Bolna.