Pricing
Book a Demo Register for a Trial
Microsoft Teams · Real-time alerts

Your Teams channel. Now with procurement intelligence.

Real-time Adaptive Card alerts for invoice approvals, payment reminders, matching exceptions and AI insights - delivered to the Teams channel your organisation already uses. Webhook setup in 60 seconds, or full Graph API control via Azure AD.

Book a Demo Connect your channel
<30s
Alert latency
2
Connection options
~60s
Webhook setup
P
Procurement > General
42 members
O
OmniPATH Bot 14:47
PO Pending Approval
Requester
Sarah Chen
Site
Old Harbour Inn
Supplier
FS Foodservice
Amount
£2,847.50
Items
14 line items
Reference
PO-2847
View in OmniPATH
O
OmniPATH Bot 15:14
Matching Exception
INV-09221 vs PO-2834 · £42.80 variance · FS Foodservice
×
OmniPATH posts to Microsoft Teams · The notification surface for the whole platform
Real-time, every time

Procurement events where your team already is.

Sub-30-second delivery. Native Adaptive Card rendering on desktop, mobile and web - no plugin install, no add-on approval, no IT ticket.

<30s
Alert latency
Fire-and-forget delivery - typically sub-second from event to Teams message
Zero
Plugin installs
Adaptive Cards render natively in Teams - no marketplace listing required, no IT approval workflow
100%
Visibility
Every procurement, invoice and finance event in one channel - desktop, mobile, web
Before vs after

The shift from "log in to check" to "see it as it happens".

The biggest finance bottleneck isn't approval logic - it's awareness latency. Teams integration removes that gap entirely.

×
Without Teams integration
The default state for most finance tools
  • Check OmniPATH manually for pending approvals
  • Approval delays - hours or days before someone notices the queue
  • Payment deadlines missed - no proactive reminders before due date
  • Duplicate invoices caught late, sometimes after they've posted
  • Constant switching between procurement and collaboration tools
✓
With Teams integration
Native Adaptive Cards in your day-to-day workspace
  • Adaptive Card alerts in the channel your team already uses
  • Approvals actioned within minutes - deep link to the OmniPATH record
  • Payment reminders fire before due date - never miss a deadline
  • Duplicates flagged before approval, never reach the ledger
  • Native rendering on desktop, mobile and web - no plugin install
Setup options

Two ways to connect. Pick your trade-off.

Most teams choose the webhook path - it's the simplest finance tooling integration there is. Larger orgs with stricter Azure AD governance go with Graph API for full token lifecycle control.

Option A · Simplest
Incoming Webhook
A direct webhook URL into your chosen Teams channel. No OAuth, no Azure AD app registration, no token refresh. Once pasted, it just works.
  • Channel owner adds an Incoming Webhook connector to the target Teams channel
  • Teams generates a webhook URL - copy it
  • Paste into OmniPATH Settings → Integrations → Teams - send a test message - done
Auth
URL only
Setup time
~60 seconds
Token expiry
Never
Storage
AWS KMS encrypted
Option B · Full control
Graph API via Azure AD
OAuth 2.0 flow via Azure AD. App registration, scope review, token lifecycle managed centrally. The path most enterprise IT teams want.
  • Admin clicks Connect Teams - OAuth flow opens in Azure AD
  • Authorise ChannelMessage.Send scope (minimum required, nothing extra)
  • Pick the team and channel from a Graph-fetched dropdown - send test - done
Auth
OAuth 2.0
Setup time
~2 minutes
Token expiry
Auto-refresh
Tenant control
Full Azure AD
Adaptive Card anatomy

Built on Adaptive Cards v1.4.

Adaptive Cards are Microsoft's native structured-message format. The same card renders identically on Teams desktop, mobile, web and even Outlook - without device-specific tuning.

01

Title block

Bold event headline. The line your team sees first when triaging the channel - clean, scannable, no emoji.

02

FactSet

Structured key-value field grid. Native Teams component - labels right-aligned, values left-aligned, automatic dark/light theme adaptation.

03

OpenUrl action

Single deep-link button - View in OmniPATH - opens the relevant record. View-only from Teams; actioning happens in OmniPATH.

04

Native rendering

No plugin install, no marketplace approval. Adaptive Cards are part of Teams itself - same card across desktop, mobile, web.

F
Finance > General
O
OmniPATHBot09:12
Payment Due in 3 Days
Supplier
Fresh Direct Ltd
Amount
£1,890.00
Due date
9 May 2026
Invoice
INV-04488
View in OmniPATH
Granular control

Per-event toggles. Per-user mutes.

Same control surface as Slack - admins choose what posts to the channel, individual users mute the events they don't want pinging them personally.

Same toggles. Identical control.

Whether you're on the webhook or Graph API path, the settings panel works the same way. Per-event toggles for all 13 event types. The defaults are tuned for normal use - high-signal events on, batch noise off - but every toggle is one click.

If you want the full event list and what each one means, the Slack integration page has the complete table - Teams supports identical events.

Connection mode
Webhook
Graph API
Procurement > General
webhook · ••••••••8a3f
Live
Event toggles · 13 types
po_pending_approval
PO awaiting sign-off
po_approved
PO signed off
matching_exception
Invoice vs PO mismatch
duplicate_invoice
Duplicate detected
supplier_verification_failed
Bank detail check failed
approval_overdue
Past SLA
payment_due_reminder
Payment approaching
batch_processing_complete
Batch finished - usually muted
expense_submitted
New claim - usually muted
Slack vs Teams

Feature parity, side by side.

Both integrations cover the same events with the same controls. The differences are technical - message format, auth model, channel selection.

Capability
Slack
Microsoft Teams
Message format
Block Kit
Adaptive Card v1.4
Authentication
OAuth 2.0
Webhook URL or OAuth
Token expiry
None (permanent)
Auto-refresh (Graph)
Setup time
~60 seconds
~60s (webhook) / ~2m (Graph)
Channel selection
Public channels dropdown
Team + channel dropdown
Event coverage
All 13 event types
All 13 event types
Per-event toggles
Yes
Yes
Per-user mutes
Yes
Yes
Deep-link button
Yes (View)
Yes (OpenUrl)
Channels per organisation
One
One
Frequently asked

The practical details.

Webhook or Graph API - which should I pick?
Webhook is simpler and faster. No Azure AD app registration, no IT ticket, no token refresh. The trade-off is governance - webhook URLs sit on the channel itself rather than under enterprise OAuth control. Graph API requires an admin to authorise the OmniPATH app in Azure AD, but tokens auto-refresh and the connection appears in your enterprise app inventory. Most teams pick webhook; larger enterprises with strict Azure AD governance pick Graph API.
Can approvers approve directly from the Adaptive Card?
Not currently. Adaptive Cards include a View in OmniPATH button that deep-links to the record where the approval can be actioned in one click. Teams acts as the awareness layer - every event surfaced in real time - and OmniPATH is where actions are taken, audited and recorded. In-channel approval via Adaptive Card actions is on the roadmap.
Does this require an admin to install something in Teams?
For the webhook path: no app install, no marketplace listing. The channel owner adds an Incoming Webhook connector to their channel - that's a built-in Teams capability available to any channel owner. For the Graph API path: yes, an Azure AD admin needs to authorise the OmniPATH app on first connect (one-time consent flow). After that, tokens refresh automatically.
Can I send different events to different channels?
Currently one channel per OmniPATH organisation. All enabled events route to that channel. Multi-channel routing - for example, finance events to one channel, procurement to another - is on the roadmap. For now, most teams use a single procurement channel that captures everything.
Is the OmniPATH app listed in Microsoft AppSource?
Not currently. The integration works via standard Teams capabilities - Incoming Webhooks (built into Teams) or Microsoft Graph API (standard Azure AD app pattern) - neither of which requires an AppSource listing. AppSource publication is something we'll consider as the integration matures, but it's not a prerequisite for use.
What scopes does OmniPATH request when using Graph API?
The minimum required: ChannelMessage.Send for posting messages, plus read-only access to Team.ReadBasic.All for the channel-selection dropdown. No mailbox access, no calendar, no SharePoint, no user data. Tokens are encrypted at rest with AWS KMS, refresh handled by TeamsAuthService, revocable from Azure AD admin centre at any time.
What if Teams goes offline or the webhook is removed?
Failed deliveries are logged but not retried automatically. Teams outages are typically brief and the in-app notification surface inside OmniPATH has the full record. If the webhook URL is rotated or the bot is removed in Graph mode, OmniPATH detects the auth failure on next dispatch and surfaces a reconnect prompt to admins. No silent failures.
Related integrations

The rest of the messaging surface.

Sister integration

Slack Integration

Same event coverage, Block Kit message format, OAuth 2.0 with permanent tokens. Includes the full event-type table.

See Slack integration
Internal messaging

Team Messaging

OmniPATH's built-in messaging - compose with attached entities, mention to assign, reach external suppliers via email.

See team messaging
Where alerts come from

Insights Agent

The autonomous monitoring layer that generates the anomaly alerts you'll see in your channel - spend spikes, unusual patterns, drift.

See the Insights Agent
Ready when you are

Connect your Teams channel in under 60 seconds.

If you're a channel owner, paste a webhook URL - done. If you need full Graph API control, the OAuth flow takes about two minutes. We'll walk you through whichever path fits your governance.

Book a Demo Start a Trial Calculate Your Savings
Teams integration included on Basic and Premium · Webhook setup in 60 seconds during the demo