Operator
← All integrations
Rootly logo+Slack logo

Connect Rootly to Slack

Automate Rootly and Slack with AI

Rootly incident timelines and Slack war rooms should stay in sync when severity changes mid response. Operator.io points OpenClaw at Rootly and Slack so incident open and resolved events post to the channel your rotation watches, Slack thread updates can append to the Rootly timeline when you log a decision from chat, and on call can ask for the live Rootly status without leaving the room. Ask what is still active and it lists Rootly incidents with their Slack thread links.

It reaches both apps directly or through connectors like Composio MCP and Pipedream MCP, which handle the sign in and token refresh, so there is no Zap to build and no API keys to paste.

What your agent can do with Rootly and Slack

What your agent does in Rootly

  • Delete Action Item

    This tool allows for the deletion of a specific action item in Rootly. It complements the existing ROOTLY_LIST_ACTION_ITEMS functionality by providing the ability to remove individual action items from the system.

  • Delete Incident

    Tool to delete an incident in Rootly by ID. Use when performing administrative cleanup. This is a destructive operation and depends on appropriate Rootly permissions.

  • Get Action Item Details

    Retrieves detailed information about a specific action item by its ID from Rootly. Action items are tasks or follow-up items created during incident management to track work that needs to be completed. This tool returns comprehensive det...

  • Get Incident Details

    Tool to retrieve full details for a single Rootly incident by ID. Use when you need complete incident information for drill-down after listing or searching incidents. Supports optional include parameter to fetch related resources like en...

  • List Action Items

    This tool retrieves a list of all action items for an organization in Rootly. Action items are tasks or follow-up items that need to be completed during or after an incident, helping to track and manage incident-related tasks effectively.

  • Update Incident

    Tool to update fields on an existing Rootly incident by ID. Use when you need to modify incident status, severity, metadata, or other attributes. Supports updating title, status, summary, severity_id, service_ids, environment_ids, and more.

What your agent does in Slack

  • Add call participants

    Registers new participants added to a Slack call.

  • Add emoji

    Adds a custom emoji to a Slack workspace given a unique name and an image URL; subject to workspace emoji limits.

  • Add an emoji alias

    Adds an alias for an existing custom emoji in a Slack Enterprise Grid organization.

  • Add Enterprise user to workspace

    Adds an Enterprise user to a workspace. Use when you need to assign an existing Enterprise Grid user to a specific workspace with optional guest restrictions.

  • Add reaction to message

    Adds a specified emoji reaction to an existing message in a Slack channel, identified by its timestamp; does not remove or retrieve reactions.

  • Add a remote file

    Adds a reference to an external file (e.g., Google Drive, Dropbox) to Slack for discovery and sharing, requiring a unique `external_id` and an `external_url` accessible by Slack.

All 145 Slack actions →

How it works

Tell the agent what you want to happen between Rootly and Slack, for example to watch one and act in the other, or to keep the two in step. It reads what it needs from Rootly, works out what to do, and runs the matching action in Slack without you mapping a single field.

You can have it run once, on a schedule, or whenever something changes. Ask it for a status any time and it reads the latest from both apps back to you in the same chat.

Common questions about Rootly and Slack

How do I connect Rootly and Slack to Operator?
You authorize Rootly and Slack once each from your Operator dashboard. Operator holds both connections and refreshes the access tokens for you, so your agent keeps working across them without you signing in again.
What can my agent do across Rootly and Slack?
Tell it the job and it moves between Rootly and Slack as one task, choosing which actions to run on each side. There is nothing to map and no trigger to configure; you give instructions the way you would to a person.
Can my agent keep Rootly and Slack in sync?
Yes. It can watch Rootly and act in Slack, or keep both in step, reading from one and running the matching update in the other. This runs on demand when you ask or on a schedule you set.
Do I need to build a workflow or write code?
No. There is no workflow to build, no fields to map, and no API keys to paste. Operator manages both connections, and you give the agent instructions in plain language.

Rootly and Slack integrations

Put your agent on Rootly and Slack

Sign in, connect both apps, and hand your agent the work. The same setup reaches every app in the catalog. Your first week is free.

Try for free