How do I upgrade or reconnect Assembled's Slack integration? – Assembled

Assembled's Slack integration has two versions: a legacy version with limited functionality and a current version that supports interactive, bidirectional workflows. This article explains what the current integration offers, who can connect it, and how to upgrade from the legacy version or reconnect if something isn't working.

What does the current Slack integration support?

The current Slack integration supports interactive, bidirectional workflows between Assembled and Slack. This includes:

One-click approvals for time-off and schedule change requests
Shift-swap buttons that agents can act on directly in Slack
Form inputs that send data back into Assembled
Push notifications for schedule updates and alerts
The /assembled now slash command to check who is currently staffed

The legacy version of the integration only supported one-way visibility — outbound notifications and a limited set of slash commands. It did not have the permissions required to receive form inputs or push changes back into Assembled.

How do I know if I'm on the legacy version?

If your Slack integration was connected more than several months ago, it may be running on the legacy version. Signs you may be on the legacy version include:

The OAuth scopes shown in Slack are limited to commands, channels:read, and similar read-only permissions
One-click approvals and shift-swap buttons are not available in Slack
The /assembled now command returns unexpected results or shows "nobody staffed" even when agents are scheduled

To confirm, go to Settings > Integrations in Assembled and review the connected Slack app. If you're unsure, contact support@assembled.com and we can check for you.

Who can connect or reconnect the Slack integration?

The person who connects the Assembled app to Slack must have Slack admin permissions in your Slack workspace. This is because the connection requires authorizing a new set of OAuth scopes that only a Slack admin can approve.

If you reconnect the integration without Slack admin permissions, the authorization may appear to succeed but the integration will remain limited to the legacy scopes.

Keep in mind: The authorized member shown in Assembled's integration settings is the Slack account that originally connected the app. To update this, you need to disconnect and reconnect the integration as described below.

How do I upgrade from the legacy version?

Upgrading requires disconnecting the existing integration and reconnecting it with a Slack admin account. This grants the new OAuth scopes the current integration requires.

In Assembled, go to Settings > Integrations.
Find the Slack integration and select Disconnect.
Have the person with Slack admin permissions sign in to Assembled.
Select Connect Integration next to Slack and complete the OAuth authorization flow in Slack.

Once reconnected, the integration will have the permissions needed for interactive features like one-click approvals and shift-swap buttons.

Note: Disconnecting the integration does not affect your schedule data or existing Assembled configuration. It only removes the Slack app authorization.

How do I verify the reconnection worked?

After reconnecting, confirm the following:

The authorized member shown in Settings > Integrations reflects the account that just reconnected
The /assembled now command in Slack returns accurate staffing information
Interactive Slack notifications (such as shift-swap requests) include actionable buttons

If the /assembled now command still shows "nobody staffed" after reconnecting, this typically means the integration isn't syncing with your schedule data yet. Wait a few minutes and try again. If the issue persists, contact support@assembled.com.

What if reconnecting doesn't fix the issue?

If you've reconnected with a Slack admin account and the integration still isn't working as expected, a few things to check:

Confirm the reconnecting account has full Slack admin permissions (not just channel admin)
Check that the Assembled app was fully authorized in Slack during the OAuth flow — look for the new scopes in your Slack app settings
Try disconnecting and reconnecting once more, making sure to complete all steps in the authorization flow

If none of these resolve the issue, reach out to support@assembled.com and share a screenshot of the OAuth scopes shown in your Slack app settings. This helps us confirm which permissions were granted.