Plans: Slack is available on the Pro and Core plans. You need to be a portal admin or admin to set it up.
Use case: your team wants a Slack message when a client submits a request, comments or pays, without keeping ManyRequests open. Your clients can also connect their own Slack workspace to follow their requests.
You create your own Slack app once, branded with your portal name. You use it for your agency's channel, and your clients use it to connect their workspaces.
How to set up Slack for your agency
Go to Settings > Integrations and click Slack.
In step 1, Create your Slack app, click Create Slack app. Slack opens with an app already set up and named after your portal. Pick your Slack workspace and create the app. You can change the app icon and description in Slack under Basic Information > Display Information.
In Slack, open Basic Information and copy the Client ID and Client Secret.
Back in ManyRequests, in step 2, Configure OAuth credentials, paste them into Client ID and Client secret and click Save credentials.
Optional, step 3: if your clients will connect their own Slack, enable public distribution in Slack. Go to Manage Distribution, expand Remove Hard Coded Information, check the box and click Activate Public Distribution. This doesn't list your app in the Slack App Directory.
In step 4, click Connect to Slack. Slack asks you to authorize the app and pick the channel for notifications.
Back on the Slack page, the badge reads Connected and you see Connected to Slack with the channel webhook. Click Test connection. A test message appears in your Slack channel.
Under Notification preferences, turn on the notifications you want and click Save changes.
Notifications you can send to Slack
Group | Notification | Sent when |
Requests notifications | New service request | A client submits a new request |
Request updated by a client | A client changes a request's priority or marks it as completed | |
New comment by team member on assigned request | A team member comments on an assigned request | |
New comment by client on assigned request | A client comments on an assigned request | |
New assigned request | A request is assigned | |
New chat message | Someone sends a new chat message (off by default) | |
Billing notifications | New client | A new client joins |
Subscriptions cancelled by client | A client cancels a subscription | |
Subscriptions set to cancel by client | A client sets a subscription to cancel at the end of its period | |
Client payment failed | A client's payment fails | |
Client payment rejected | A client's payment is rejected | |
Payment confirmation | A payment is processed | |
Subscription paused | A subscription is paused | |
Subscription created | A new subscription is created |
Pause, change channel or disconnect
Pause: turn off Enabled next to Webhook configuration. 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. This removes the Slack connection.
How clients connect their own Slack
Organization owners can send notifications about their organization to their own Slack workspace. This works once you have saved your app credentials (step 2) and enabled public distribution (step 3).
The client goes to Settings > Profile and account and opens the Integrations tab. Only organization owners see it.
Under Organization integrations, they click Slack, then Connect to Slack, and pick a channel.
They choose their Notification preferences and save.
Clients can get notifications about new comments, completed requests, new requests, trials ending, renewal reminders, failed or rejected payments, payment confirmations and new chat messages. The settings apply to the whole organization.
Troubleshooting
I see "This integration was disabled automatically".
ManyRequests turns Slack off after 5 failed deliveries in a row, for example when the channel or app was deleted in Slack. Fix the cause, then click Reconnect to different channel or turn Enabled back on and save. Use Test connection to check.
Connect to Slack is greyed out.
Save your Client ID and Client secret in step 2 first.
My client doesn't see the Integrations tab.
Check that they own the organization, that your app credentials are saved and that your plan includes Slack.
My client can't install the app in their workspace.
Enable public distribution for your Slack app (step 3).