Copy Markdown

What you'll accomplish

Connect solarOS to your Slack workspace, then decide which events post to which channels: team-wide notifications, routing by work type or assignee, and technician @-mentions.

Prerequisites

• The Owner or Admin role. Connecting, configuring, and testing Slack all require the settings.integrations.manage permission, which only Owner and Admin hold by default.
• A Slack workspace you can install apps into.

Steps

1. Start the connection

Go to Settings → Integrations, open the integrations catalog (the Discover or Installed tab), find the Slack card, and click Connect. That takes you to the Slack integration page.

2. Connect the workspace

Click Connect to Slack and complete Slack's OAuth consent screen. You're redirected back to solarOS, which shows a Connection Status card with a status badge: Pending, Active, Paused, Error, or Disconnected.

3. Add @solarOS to your channels

In Slack, run /invite @solarOS in every channel you want solarOS to post to. Back on the Slack integration page, the Connected channels card lists channels the app has been added to. Click Refresh connected channels after inviting it somewhere new.

4. Link team members

On the Team members in Slack card, click Match by email to link solarOS team members to their Slack accounts by matching email addresses. Linked members can be @-mentioned in notifications; technicians need this for field-update messages to reach them directly. You can also edit members directly from Settings → Team (linked from this card).

5. Set a default channel

On the Default Channel card, enter a Channel ID (find it in Slack's channel details) and click Save Default Channel. Notifications with no channel of their own, and technician updates when the technician has no channel mapped, post here.

6. Configure notification rules

In the Slack notifications panel, click New Slack notification. Each notification pairs:

1. A Trigger (e.g. "New opportunity", "Technician arrived").
2. Optional Conditions that narrow it down.
3. A Send to destination (one or more Channel IDs).
4. A Message template.

Click Create notification. Existing rules can be toggled active/inactive inline, or opened to Save changes.

7. Configure routing rules (optional)

In the Routing Rules panel, click Add Rule to route by Work type or Assignee to a specific channel. Routing rules are checked before a notification rule's own destination. Click Save Routing Rules when done.

8. Send a test message

On the Test Message card, click Send Test Message to confirm the bot can post in the configured channel. You can also send a test for an individual notification rule from its edit drawer (Send test).

Verify it worked

• The Connection Status badge reads Active.
• Send Test Message succeeds and the message arrives in the channel you configured.

Common problems

• Status badge shows Error. The connection needs to be re-authorized: click Reconnect Slack. Common causes: the Slack app was uninstalled from the workspace, or its token was revoked.
• Test message fails with "Invite @solarOS to this channel in Slack (/invite @solarOS), then retry." Run /invite @solarOS in that Slack channel, then retry.
• Test message fails with "No channel with that ID - check the Channel ID." Double check the Channel ID: it's not the channel name.
• A banner says "Reconnect Slack to pick channels from a list" (or "look up people"). The workspace approved an earlier, narrower permission set. Click Reconnect: posting still works in the meantime, but channel/member pickers won't populate until you do.
• No channels show up in Connected channels. solarOS only sees channels it's been explicitly invited to. Run /invite @solarOS in each one you want to use, then click Refresh connected channels.