Plans: Slack is available on the Pro and Core plans. Your agency sets up its Slack app once. After that, each organization owner can connect their own Slack workspace.
Use case: your client's marketing team lives in Slack. Instead of waiting for emails, they want a message in their own channel when you comment on a request, finish one, or send an invoice reminder. The message comes from your branded Slack app, not from ManyRequests.
This article has two parts: what your agency sets up first, and the steps you can share with your clients.
What your agency sets up first
You need to be a portal admin or admin.
Set up Slack for your agency: create your Slack app and save its Client ID and Client secret under Settings > Integrations > Slack. See How to set up Slack integration. Clients can only connect once these credentials are saved.
On the same page, follow step 3, Enable public distribution (optional). In your Slack app settings, go to Manage Distribution, expand Remove Hard Coded Information, check the box and click Activate Public Distribution. Without this, your app can only be installed in your own Slack workspace, so clients can't connect theirs. It doesn't list your app in the Slack App Directory.
Let your organization owners know they can connect Slack, and share the steps below.
How clients connect their Slack
Only the owner of an organization can connect Slack. The connection applies to the whole organization: everyone in it sees the notifications in the channel the owner picks.
In the portal, go to Settings > Profile and account.
Open the Integrations tab. Under Organization integrations, click Slack.
Click Connect to Slack. Slack opens and asks you to allow the app and pick the channel for notifications. Choose a channel and allow.
You're taken back to the portal. The badge now reads Connected, and you see Connected to Slack with the channel's webhook. Click Test connection to send a test message to the channel.
Under Notification preferences, turn off anything you don't want in Slack and click Save changes. All notifications start turned on, except New chat message.
Notifications clients can send to Slack
Group | Notification | Sent when |
Requests notifications | New comment | Someone on the agency team comments on one of your requests |
Service request has been completed | A request is marked as completed | |
New service request | A new request is submitted for your organization | |
New chat message | Someone sends you a new chat message (off by default) | |
Billing notifications | Payment confirmation | A payment is processed |
Subscription trial will end | A subscription trial is about to end | |
Subscription renewal reminder | Before a new invoice is issued to you | |
Payment failed | A payment fails | |
Payment rejected | A payment is rejected |
Pause, change channel or disconnect
Pause: turn off Enabled next to Webhook configuration and save. Notifications stop, but the connection stays. The badge reads Connected (Paused).
Change channel: click Reconnect to different channel and pick another channel in Slack.
Disconnect: click Disconnect at the bottom of the page and confirm. Your organization stops getting Slack notifications.
Troubleshooting
The client doesn't see the Integrations tab.
Check three things: the client owns the organization (members don't see the tab), your agency has saved its Slack app credentials, and your plan includes Slack.
The client sees "Slack integration is not available."
Your agency hasn't finished setting up its Slack app. Save the Client ID and Client secret on your Slack settings page.
Slack says the app can't be installed in this workspace.
Public distribution isn't turned on for your Slack app. Follow step 3 above.
The page says "This integration was disabled automatically".
Slack notifications stop after 5 failed deliveries in a row, for example when the channel was deleted. Click Reconnect to different channel or turn Enabled back on and save, then use Test connection.