Integrations/Communications/Slack
AO
Sl
NativeCommunicationsReal-time

Slack + AssetOS

High-priority work orders post to the channel you pick with a one-click acknowledge button. P1 outages page on-call. Nobody has to remember to check the CMMS at 2am — the alert comes to where the team already lives.

View docs

Quick facts

Built by
AssetOS · Native
Version
v3.4.1 · Apr 2, 2026
Sync direction
Push + interactive
Frequency
Real-time · <1s
Auth
Slack OAuth 2.0
Plans
Team & above
Actions
3 (Ack · Comment · Close)
Triggers
12 event types
Price
Included · no add-on
What a Slack message looks like

Actionable in one click.
Right from the channel.

Not a notification-shaped link back to another tool. Ack, comment, and close — without leaving Slack. Every action is attributed to the Slack user in AssetOS audit logs.

#maintenance-alerts
AO
AssetOSAPP2:14 AM
🚨 New P1 work order created on Pump 4B — automatic alarm from vibration sensor.
Work order · WO-2026-04118
Pump 4B vibration exceeds threshold (4.2mm/s)
Asset: Pump 4B · Building 2 · Bay 4Priority: P1Source: Sensor alarm
MT
Mira Tanaka2:17 AM
Got it — heading down. Will report back in 15.
AO
AssetOSAPP2:17 AM
WO-2026-04118 acknowledged by @Mira Tanaka · status → In progress
What the integration does

Six capabilities. Configured per-channel.

You decide which events go to which channels, who gets DMed for P1s, and what's noisy enough to batch into a daily digest. No global “all or nothing” toggle.

Channel alerts

Post new work orders to the channels you pick, filtered by priority, asset group, or location. Map once, forget forever.

Interactive actions

Acknowledge, assign, comment, or close work orders without leaving Slack. All actions attributed to the Slack user in AssetOS audit logs.

On-call paging

P1 work orders escalate to the Slack user currently on-call (from your rota) with a DM and a phone-friendly mention.

Daily digests

Open WOs, overdue PMs, parts below min — as a single scheduled post per channel. Configurable per time zone.

Approval workflows

PO approvals and change requests land in a channel with Approve/Reject buttons. Threshold-based routing included.

Slash commands

/assetos wo 4118 pulls a card inline. /assetos search pump lists matches. Seven commands total.

Set it up in four steps.

No developer required. Workspace admin access is enough.

Typical setup time: 4 minutes
Step 01

Click "Add to Slack"

Standard OAuth — you pick the workspace. We ask for chat:write, commands, and users:read.

Step 02

Pick your default channel

Where the bot posts when no rule matches. Usually #maintenance-alerts. Create it first if needed.

Step 03

Add routing rules

Optional — send P1s to #on-call, PM reminders to #schedules, approvals to #finance.

Step 04

Test it

Click "Send test alert". Bot posts to your default channel with a live acknowledge button. You're done.

Every trigger and action, listed.

If it's not here, it's not supported — we'd rather tell you plainly than sell you “integrates deeply” and have you find out later. Anything missing? Request it.

Triggers · AssetOS → Slack12
  • work_order.created
    Posts a new WO to mapped channels with quick actions
  • work_order.assigned
    DMs the assignee with the WO card
  • work_order.status_changed
    Threaded reply when status changes
  • pm.schedule.overdue
    Daily roll-up of overdue preventive maintenance
  • asset.location_changed
    Fires when an asset transfers between sites
  • sensor.reading.alarm
    Real-time alarm escalates to P1 channel
Actions · Slack → AssetOS3
  • Acknowledge
    Click the "Acknowledge" button to mark WO as seen + attribute to Slack user
  • Comment
    Thread replies on the Slack post sync as WO comments
  • Close
    Close from the card with optional completion notes + attribution
Plus 7 slash commands — see docs

We use cookies to analyze site traffic and improve your experience. Learn more