What you’ll get: Once connected, your team can mention
@ewake in any channel for on-demand investigation help. Ewake will also deliver On-Call Agent alerts and Scheduled Task reports directly in Slack.Two ways to connect
| Option | When to use it |
|---|---|
| From Ewake organisation | Default. One-click OAuth — simplest. |
| From a manifest | Slack admin blocks non–first-party / Marketplace apps; org requires internally-created apps. |
Option 1 — From Ewake organisation
Recommended unless your Slack admin policy blocks third-party apps.Choose From Ewake organisation
Select From Ewake organisation. You’ll be redirected to Slack’s OAuth authorization page.

Review and authorize
Review the requested permissions and click Allow.Ewake requests the following Slack permissions:
- Read messages in channels where Ewake is added
- Post messages and replies in channels
- Send direct messages to users
- Read workspace member list
Option 2 — From a manifest (custom app)
Use this when your Slack admins only allow apps your own workspace owns (i.e. they block apps that aren’t listed in the Slack Marketplace). Instead of installing Ewake’s shared Slack app via OAuth, you create your own internal Slack app from a manifest Ewake provides and hand Ewake its bot token. Functionally it’s identical to the standard install — Ewake reads channels and posts messages using the bot token, and Slack’s API doesn’t care which app issued it.Open Connect Slack in Ewake
In your Ewake dashboard, go to Integrations → Slack → Connect Slack, then choose From a manifest.
Copy the manifest
Copy the manifest shown in the dialog. It’s pre-filled for your environment — don’t use a manifest from another source.
Create the app in Slack
Open api.slack.com/apps → Create New App → From a manifest. Select your workspace, paste the manifest, and create the app.
Add the app icon
Manifests can’t set the icon. Under Basic Information → Display Information, upload the Ewake icon (otherwise the app shows a blank icon).
What Ewake does with the token
- Verifies the token and reads the workspace identity (
auth.test) - Confirms the app was granted the required bot scopes. If any are missing, the install is rejected and the missing scopes are listed.
- Stores the bot token securely and binds Ewake to your workspace
@ewake to the channels you want it to work in.
Troubleshooting
“Missing required Slack scopes” — add the listed scopes under OAuth & Permissions, click Reinstall to Workspace, then paste the newxoxb- token.
“Invalid Slack token” — make sure you copied the Bot User OAuth Token (xoxb-…), not an App-Level token (xapp-…) or user token (xoxp-…).
Ewake isn’t responding in a channel — invite @ewake to that channel; the bot only reads channels it’s a member of.