# AtomicWork + Slack integration > Bring IT service management into the tools your employees already use every day — no portal switching required. **Canonical page:** https://tray.ai/connectors/atomicwork-slack-integrations/ **AtomicWork connector:** https://tray.ai/connectors/atomicwork-integrations/ **AtomicWork documentation:** https://tray.ai/documentation/connectors/service/atomicwork **Slack connector:** https://tray.ai/connectors/slack-integrations/ **Slack documentation:** https://tray.ai/documentation/connectors/service/slack ## Overview AtomicWork is a modern AI-powered IT service management platform. Slack is where your teams communicate and get work done. When you connect them, employees can submit tickets, check request status, and get IT support without leaving Slack, while IT teams manage everything centrally in AtomicWork. No more fragmented help desk workflows — just a conversational service experience that fits how people actually work. The biggest friction in IT service management is the gap between where employees work and where IT support lives. When someone has to leave Slack, open a browser, navigate a portal, and fill out a form, ticket volume drops and shadow IT rises. Integrating AtomicWork with Slack closes that gap. New tickets created in Slack flow instantly into AtomicWork with full context, approvals happen in real time through Slack messages, and IT agents get immediate notifications when SLAs are at risk. Faster resolution times, happier employees, a more efficient IT team — and nobody has to change how they work to get there. ## Use cases ### Employee Self-Service Ticketing from Slack Employees can submit IT requests and incidents directly from a Slack slash command or message shortcut, which automatically creates a fully categorized ticket in AtomicWork. The employee gets a threaded Slack confirmation with their ticket ID and estimated resolution time. No portal login, no friction — just help, fast. - Increases ticket submission rates by reducing effort for employees - Eliminates manual re-entry of request details by IT agents - Populates AtomicWork tickets with Slack user metadata automatically ### Real-Time Ticket Status Updates in Slack When an AtomicWork ticket changes status — open to in-progress, in-progress to resolved — the employee who filed the request gets an automatic Slack DM with the update. IT teams can configure which status transitions trigger notifications, keeping employees informed without flooding their inbox. - Reduces inbound 'what's the status?' follow-up messages by up to 80% - Keeps employees informed without requiring them to check the portal - Frees IT agents from repetitive status communication tasks ### SLA Breach Alerts to Slack Channels When an AtomicWork ticket is approaching or has breached its SLA threshold, an automated alert posts to a designated Slack channel — like #it-escalations — tagging the assigned agent and their manager. High-priority issues don't get buried in a queue, and response times stay where they need to be. - Prevents SLA breaches from going unnoticed in high-volume queues - Creates immediate accountability with tagged Slack notifications - Lets IT leads prioritize work without manually monitoring dashboards ### Approval Workflows via Slack Messages When an AtomicWork request needs manager or IT admin approval — software procurement, access provisioning — the approver automatically gets a Slack message with request details and interactive approve or reject buttons. Their response is instantly recorded in AtomicWork, moving the ticket forward without any portal access required. - Cuts approval cycle time from days to minutes - Keeps a full audit trail in AtomicWork regardless of where approval happens - Increases approval response rates by meeting approvers in Slack ### New Employee Onboarding Request Automation When HR triggers a new hire workflow or a record is created in your HRIS, the integration can automatically open a structured onboarding ticket in AtomicWork and post a welcome notification to the new employee's Slack account. IT provisioning steps are tracked in AtomicWork while communication flows through Slack. - Ensures every new hire gets consistent IT onboarding without manual setup - Reduces onboarding provisioning time with pre-built ticket templates - Gives new employees a friendly, Slack-native first interaction with IT ### Incident Management and Broadcast Alerting When a P1 or P2 incident is raised in AtomicWork, the integration automatically posts a formatted incident alert to a Slack incident channel, creating a shared war room thread. Updates to the incident record — owner changes, status updates, resolution notes — appear in the thread in real time, so every stakeholder stays current. - Centralizes incident communication without requiring a separate tool - Keeps non-technical stakeholders informed with plain-language Slack updates - Speeds up mean time to resolution by accelerating team coordination ### IT Knowledge Base Search from Slack Employees can query the AtomicWork knowledge base directly from Slack using a natural language message, with the integration surfacing the top matching articles as Slack message blocks. If no article resolves the issue, a ticket is automatically created from the same conversation, capturing full context including the search query and conversation history. - Deflects repetitive tickets by enabling self-service knowledge discovery - Captures rich context when escalation to a ticket is needed - Improves knowledge base utilization metrics tracked in AtomicWork ## Templates ### Slack Message to AtomicWork Ticket Automatically creates a new AtomicWork support ticket whenever an employee sends a message to a designated Slack support channel or uses a specific emoji reaction. The ticket is populated with the Slack user's name, department, message content, and any attached files, and a confirmation thread is posted back to the employee. Connectors used: AtomicWork, Slack ### AtomicWork Ticket Update to Slack DM Sends a personalized Slack direct message to the ticket requester whenever their AtomicWork ticket status changes, is reassigned, or a comment is added by an agent. Keeps employees in the loop without requiring them to monitor the service portal. Connectors used: AtomicWork, Slack ### AtomicWork SLA Alert to Slack Channel Monitors AtomicWork for tickets nearing or past their SLA deadlines and sends a formatted alert to a configured Slack channel, tagging the assigned agent and IT manager. Includes ticket priority, time elapsed, and a direct link to the AtomicWork record. Connectors used: AtomicWork, Slack ### Slack-Based Approval Flow for AtomicWork Requests When an AtomicWork ticket enters a pending approval state, this template automatically sends an interactive Slack message to the designated approver with full request context and one-click approve or reject buttons. The decision is written back to AtomicWork and the ticket moves to the next workflow stage automatically. Connectors used: AtomicWork, Slack ### P1 Incident Slack War Room Creator When a Priority 1 incident is opened in AtomicWork, this template instantly posts a formatted incident brief to a dedicated Slack incident channel and optionally creates a Slack canvas or thread for the war room. All subsequent AtomicWork status changes on the incident are automatically echoed into the thread. Connectors used: AtomicWork, Slack ### New Hire IT Onboarding Ticket and Slack Welcome Triggered by a new employee record creation event — from an HRIS or manual trigger — this template creates a structured onboarding checklist ticket in AtomicWork and sends a Slack DM to the new hire introducing them to IT support resources and their ticket ID. Connectors used: AtomicWork, Slack ## Challenges Tray.ai solves ### Bidirectional Data Sync Without Duplication When Slack messages trigger AtomicWork ticket creation and AtomicWork updates push notifications back to Slack, there's a real risk of feedback loops where notifications trigger additional events, leading to duplicate tickets or infinite message chains. **How Tray.ai helps:** Tray.ai's workflow logic includes built-in deduplication controls and conditional branching. You can set event source flags, filter on specific trigger conditions, and use tray.ai's stateful data stores to track which events have already been processed — so every message creates exactly one ticket and every update sends exactly one notification. ### Mapping Slack Users to AtomicWork Requesters Slack users are identified by user IDs and display names, while AtomicWork tickets require requester records tied to email addresses or internal employee IDs. Mismatches between these identity models can cause tickets to be created without a valid requester or assigned to the wrong person. **How Tray.ai helps:** Tray.ai has a user lookup step that resolves Slack user IDs to email addresses via the Slack API, which can then be matched against AtomicWork requester records. You can build fallback logic to create a new requester profile in AtomicWork if no match is found, so no ticket is ever orphaned. ### Handling Slack Interactivity and Button Payloads Interactive Slack messages with approve/reject buttons require correctly parsing Slack's interactive payload format, verifying request signatures, and responding within Slack's three-second acknowledgment window — which gets tricky fast when backend workflows are involved. **How Tray.ai helps:** Tray.ai handles Slack webhook ingestion and signature verification natively. Its asynchronous workflow execution model means complex multi-step processes — looking up an approver in AtomicWork, updating a ticket — run in the background while the initial acknowledgment goes back to Slack immediately, preventing timeout errors. ### Managing High-Volume Slack Channels Without Noise In large IT teams, posting every AtomicWork ticket update to a shared Slack channel creates notification overload. Agents start ignoring the channel, and genuinely urgent alerts get lost in the noise. **How Tray.ai helps:** Tray.ai lets you build sophisticated filtering and routing logic into your workflows. Route P1 and P2 updates to a high-visibility #it-critical channel, send routine status updates only as direct messages to the requester, and suppress notifications for low-priority ticket state changes — so every update gets the right level of visibility. ### Maintaining Audit Trails Across Both Platforms When approvals, escalations, and status changes happen through Slack interactions, those decisions and timestamps need to be recorded back in AtomicWork to maintain a complete audit trail for compliance and reporting. Without that write-back, AtomicWork records become incomplete. **How Tray.ai helps:** Every tray.ai workflow that captures a Slack interaction includes a dedicated write-back step that records the action, timestamp, actor identity, and outcome in the relevant AtomicWork ticket or request record. AtomicWork stays the system of record regardless of where the action was taken, which keeps audit and compliance requirements intact. ## Learn more - Intelligent Integration: https://tray.ai/platform/intelligent-ipaas/ - Merlin Agent Builder: https://tray.ai/platform/merlin-agent-builder/ - Agent Gateway for MCP: https://tray.ai/platform/agent-gateway/ - Book a demo: https://tray.ai/contact/