Pricing
Slack Integration · Real-time alerts

Your ops channel. Now with procurement intelligence.

Real-time alerts for invoice approvals, payment reminders, matching exceptions and AI insights - delivered as rich Block Kit messages to the Slack channel your team already lives in.

<30s
Alert latency
13
Event types supported
~60s
To connect
#procurement
12 members
O
OmniPATH App 2:47 PM
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 App 3:14 PM
Matching Exception
INV-09221 vs PO-2834 · £42.80 variance · FS Foodservice
×
OmniPATH posts to Slack · The notification surface for the whole platform
Real-time, every time

Procurement events where your team already is.

Sub-30-second delivery. Zero tab-switching. Every event your finance and ops people care about, surfaced in the channel they have open all day anyway.

<30s
Alert latency
Fire-and-forget delivery - typically sub-second from event to Slack message
Zero
Missed approvals
Overdue reminders fire automatically when items pass SLA - nothing stuck in a queue
100%
Visibility
Every procurement, invoice and finance event in one place - single channel, single view
Before vs after

The difference finance teams feel.

The shift from "log in to check" to "see it as it happens" is the difference between a tool you remember to use and a tool that just works.

×
Without Slack integration
The default state for most finance tools
  • Check OmniPATH manually for pending approvals
  • Approval delays - hours or days before someone notices a queue is building
  • Payment deadlines missed - no proactive reminders before due date
  • Duplicate invoices caught late - sometimes after they've posted to accounting
  • Constant tab-switching between procurement tool and team chat
  • Operations people log in to check, finance people log in to chase
With Slack integration
When OmniPATH meets the team where they work
  • Instant alerts in the channel your team already uses every day
  • Approvals actioned within minutes - one click from Slack to the OmniPATH record
  • Payment reminders fire before due date - never miss a payment deadline
  • Duplicates flagged before approval, never reach the ledger
  • Block Kit formatting - structured, scannable, mobile-readable
  • Team naturally responds in-thread, conversation lives where the work lives
Event coverage

Thirteen event types. One channel.

Every procurement, invoice, finance and AI insight event in OmniPATH can post to Slack. Per-event toggles in settings - turn on what your team needs, mute what they don't.

Procurement events
3 event types
po_pending_approvalPO awaiting approval - tagged with requester, site, supplier and amount
po_approvedPO signed off - with approver name and timestamp
po_rejectedPO rejected - with approver name and reason given
Invoice processing
4 event types
batch_processing_completeDocument batch finished - count and processing time
matching_exceptionInvoice vs PO discrepancy - variance amount and which fields differ
duplicate_invoicePossible duplicate detected - vendor, amount, date match details
supplier_verification_failedBank detail mismatch - supplier name and the field that failed
Finance alerts
5 event types
approval_overdueApproval past SLA - submitter, approver and days aged
payment_due_reminderPayment due - supplier, amount and days until due
expense_submittedNew expense claim - submitter, amount and category
expense_approvedExpense approved - submitter and approver
expense_rejectedExpense rejected - submitter, approver and reason
AI insights
1 event type + roadmap
new_featuresPlatform updates - release notes posted as they ship
insights_alertInsights Agent anomaly - spend spikes, unusual patterns, drift detection
Block Kit anatomy

Built using Slack's native format.

Block Kit is Slack's own structured-message language. OmniPATH uses it natively, which means messages render the same on desktop, mobile and notifications - and search results show the structured fields, not stripped plain text.

01

Header block

Event title - bold, scannable, emoji-free. The line your team's eye lands on first when triaging the channel.

02

Section block

Structured body fields formatted as mrkdwn. Two-column field grid for quick scanning - requester, site, amount, reference.

03

Action button

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

04

Fallback text

Plain-text version included for push notifications, search indexing and accessibility readers. Same key facts, no formatting.

#finance
O
OmniPATHApp9:12 AM
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.

Workspace admins choose which event types post to the channel. Individual users can mute event types from their own notification preferences - without affecting anyone else.

Configure once. Tune as you go.

Out of the box, the most useful events are on (approvals, exceptions, payment reminders) and the noisier ones are off (batch completions, every expense submission). Tune them to fit how your team triages - every toggle is one click.

If a notification type is creating noise, any user can mute it from their own notification preferences page. The channel keeps receiving - they just stop being pinged personally.

Connection
acme-hospitality.slack.com
#procurement
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
One-time setup

Connect in under 60 seconds.

OAuth 2.0 to your workspace, pick a channel, done. Slack bot tokens are permanent - no expiry, no refresh, no maintenance.

Step 01

Click Connect Slack

Workspace admin opens Settings → Integrations → Slack and clicks Connect. OAuth flow begins.

Step 02

Authorise in Slack

Standard Slack OAuth screen. OmniPATH requests chat:write and channels:read - minimum required scopes, nothing extra.

Step 03

Pick a channel

Dropdown of public channels the bot can see. Pick the target. Send a test message to verify. You're live.

Under the hood

The bits your IT team will ask about.

Standard OAuth, encrypted tokens, minimum scopes, no surprises. Everything documented in the technical handbook.

OAuth 2.0
Auth via Slack's oauth.v2.access. Bot tokens are permanent - no expiry or refresh handling needed.
Encrypted at rest
Bot tokens stored encrypted with AWS KMS. TLS 1.3 in transit. Revocable from auth.revoke.
Fire-and-forget dispatch
Async chat.postMessage via NotificationService. Sub-second from event to delivery in normal load.
Rate-limit safe
Slack allows 1 message/sec per channel. Dispatch logic respects limits - no batching needed in normal operation.
Frequently asked

The practical details.

Can approvers approve directly from Slack?
Not currently. Slack messages include a View in OmniPATH button that deep-links straight to the record where the approval can be actioned in one click. Slack acts as the awareness layer - every event surfaced in real time - and OmniPATH itself is where actions are taken, audited and recorded. Direct in-channel approval is on the roadmap.
Can I send different events to different channels?
Currently one workspace, one channel per OmniPATH organisation. All enabled events route to that channel. Multi-channel routing - for example, send finance events to #finance and procurement events to #procurement - is on the roadmap. For now, most teams use a single #procurement-ops channel which captures everything.
What happens to existing notifications inside OmniPATH if I turn on Slack?
Nothing changes. In-app notifications and email alerts continue exactly as before - Slack adds a parallel channel, it doesn't replace anything. Per-user notification preferences let people choose which channels (in-app, email, Slack) receive which events. Same control surface for all three.
Can users mute specific event types personally?
Yes. The channel posts what the admin configures, but each user has their own notification preferences for personal mentions. So a finance lead can mute batch_processing_complete for their personal pings while the channel keeps receiving them for general visibility.
Does it work with private channels?
The current channel selector lists public channels the bot has access to. To post into a private channel, invite the OmniPATH bot user into the channel first (/invite @OmniPATH in the channel) - then it appears in the dropdown. The bot only sees channels it's been invited to, in line with Slack's least-privilege model.
What if the Slack workspace goes offline or the bot is removed?
Failed deliveries are logged but not retried - Slack outages are typically short and the in-app notification surface has the full record anyway. If the bot is removed from the workspace or channel, OmniPATH detects the auth failure on next dispatch and surfaces a reconnect prompt to admins. No silent failures.
Is the integration available on every plan?
Slack integration is included on Basic and Premium plans (one workspace, one channel). It's not part of the Free tier. Microsoft Teams is included on the same plans with the same scope.
Ready when you are

Connect your Slack workspace in under 60 seconds.

One OAuth click, pick a channel, send a test message. We'll walk you through it on the call - bring the workspace admin, you'll be live before the demo ends.

Slack integration included on Basic and Premium · Connect in 60 seconds during the demo