Integrations · Slack
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.
Real-time, every time
Procurement events where your team already is.
Sub-30-second delivery and no tab-switching. Every event your finance and operations people care about, in the channel they have open all day anyway.
Alert latency
Under 30 seconds
Fire-and-forget delivery, typically under a second from event to Slack message.
Reminders
No missed approvals
Overdue reminders fire automatically when items pass SLA, so nothing sits stuck in a queue.
Visibility
Every event, one channel
Every procurement, invoice and finance event in one place: a single channel, a single view.
Before and 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 building
- Payment deadlines missed, with no reminders before the due date
- Duplicate invoices caught late, sometimes after they’ve posted to accounting
- Constant tab-switching between the procurement tool and team chat
- Operations people log in to check, finance people log in to chase
With Slack integration
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 before the due date
- Duplicates flagged before approval, so they never reach the ledger
- Block Kit formatting: structured, scannable and readable on mobile
- The team responds in-thread, so the 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 it doesn’t.
3 event types
Procurement events
- po_pending_approval PO awaiting approval, with requester, site, supplier and amount
- po_approved PO signed off, with approver name and timestamp
- po_rejected PO rejected, with approver name and reason given
4 event types
Invoice processing
- batch_processing_complete Document batch finished, with count and processing time
- matching_exception Invoice and PO discrepancy, with variance and the fields that differ
- duplicate_invoice Possible duplicate, with vendor, amount and date match details
- supplier_verification_failed Bank detail mismatch, with supplier name and the failed field
5 event types
Finance alerts
- approval_overdue Approval past SLA, with submitter, approver and days aged
- payment_due_reminder Payment due, with supplier, amount and days until due
- expense_submitted New expense claim, with submitter, amount and category
- expense_approved Expense approved, with submitter and approver
- expense_rejected Expense rejected, with submitter, approver and reason
1 event type, plus the roadmap
AI insights
- new_features Platform updates: release notes posted as they ship
- insights_alert Insights Agent anomalies: spend spikes, unusual patterns and drift (on the roadmap)
Block Kit anatomy
Built using Slack’s native format.
Block Kit is Slack’s own structured-message language. OmniPATH uses it natively, so messages render the same on desktop, mobile and notifications, and search results show the structured fields, not stripped plain text.
- Header block. The event title: bold, scannable and emoji-free.
- Section block. Structured body fields in a two-column grid: requester, site, amount and reference.
- Action button. One deep-link button, View in OmniPATH. View-only from Slack; actioning happens in OmniPATH.
- Fallback text. A plain-text version for push notifications, search indexing and screen readers.
#procurement
Illustrative| Field | Value |
|---|---|
| Alert | PO pending approval |
| Requester | Sarah Chen |
| Site | Old Harbour Inn |
| Supplier | FS Foodservice |
| Amount | £2,847.50 |
| Items | 14 line items |
| Reference | PO-2847 |
Granular control
Per-event toggles. Per-user mutes.
Workspace admins choose which event types post to the channel. Out of the box, the most useful events are on (approvals, exceptions and payment reminders) and the noisier ones are off (batch completions and every expense submission). Every toggle is one click.
If a notification type is creating noise, any user can mute it from their own notification preferences. The channel keeps receiving it; they just stop being pinged personally.
Event toggles · 13 types
Illustrative| Event | What it means |
|---|---|
| po_pending_approval | PO awaiting sign-off |
| po_approved | PO signed off |
| matching_exception | Invoice and 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 set-up
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.
Under the hood
The bits your IT team will ask about.
Standard OAuth, encrypted tokens and minimum scopes. No surprises.
OAuth 2.0
Auth through Slack’s oauth.v2.access. Bot tokens are permanent, so no expiry or refresh handling is needed.
Encrypted at rest
Bot tokens stored encrypted with AWS KMS, TLS 1.3 in transit and revocable through auth.revoke.
Fire-and-forget dispatch
Asynchronous chat.postMessage calls, typically under a second from event to delivery under normal load.
Rate-limit safe
Slack allows one message a second per channel. Dispatch respects the limit, with no batching needed in normal operation.
Related integrations
The rest of the messaging surface.
Sister integration
Microsoft Teams
Same event coverage and per-event toggles, delivered as Adaptive Cards. Webhook set-up or OAuth through Azure AD.
Internal messaging
Team Messaging
OmniPATH’s built-in messaging: compose with attached records, mention to assign and reach external suppliers by email.
Where alerts come from
Insights Agent
The autonomous monitoring layer behind the anomaly alerts you’ll see in your channel: spend spikes, unusual patterns and drift.
What the books looked like before the gate.
Day zero is sealed from the accounting system before OmniPATH changes anything. This is what one year of ledger data looked like going in.
of profiled spend belonged to suppliers keyed under more than one name: one retailer four ways, a food supplier twice, another with a typo.
supplier contacts in the accounting system carried no spend in the sealed year. Every dormant record is a door left open.
of a year's ledger spend was a total on a bill. The largest supplier, nearly a third of profiled spend, had no lines at all.
of spend seen is VAT at stake on rate mismatches. The customer has already actioned 4.0%; 4.6% is still open.
of the year's bills carried a date still in the future when the baseline was sealed. Each one pulls spend into the wrong period.
of profiled spend went to supermarkets, outside any agreed price or catalogue.
From the sealed day-zero epoch of one live single-site hospitality operator (sealed 10 Sep 2026, covering the previous 12 months) and the findings read on 23 Oct 2026. Supplier groupings are our reading of the sealed spend records. How we measured this
Questions
The practical details.
Can approvers approve directly from Slack?
Not currently. Slack messages include a View in OmniPATH button that deep-links to the record, where the approval can be actioned in one click. Slack is the awareness layer, with every event surfaced in real time, and OmniPATH 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 there is one workspace and one channel per OmniPATH organisation, and all enabled events route to that channel. Multi-channel routing (for example finance events to #finance and procurement events to #procurement) is on the roadmap. For now, most teams use a single #procurement-ops channel that collects 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 or Slack) receive which events.
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. A finance lead can mute batch_processing_complete for their personal pings while the channel keeps receiving it for general visibility.
Does it work with private channels?
The channel selector lists public channels the bot can access. To post into a private channel, invite the OmniPATH bot into it first (/invite @OmniPATH), and 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 usually short and the in-app notification surface has the full record. If the bot is removed from the workspace or channel, OmniPATH detects the auth failure on the next dispatch and shows admins a reconnect prompt. No silent failures.
Connect your Slack workspace in under 60 seconds.
One OAuth click, pick a channel, send a test message. Bring the workspace admin to the demo and you'll be live before it ends.
No minimum term · UK-based support