Connecting Slack to OneClik
Send bug reports and feedback to a Slack channel — set up once, verify it works, and know exactly what to do if a message shows up without its screenshot.
Before you start
- Owner or admin access to the Slack workspace you want to connect.
- A OneClik workspace admin role — the connection page is admin-only.
- A channel already picked out — public is simplest for a first connection.
1Create the Slack app
1Open Slack's app dashboard
Go to api.slack.com/apps while signed into the Slack workspace you're connecting, then choose Create New App.
2Start from scratch
Pick From scratch over a manifest or template — OneClik only needs a handful of bot scopes, and building from scratch keeps the app free of anything unused.
3Name it and pick the workspace
Name the app something your teammates will recognize in the channel — OneClik or OneClik Bugs works well, since this is the name every message will post under. Select the target workspace and create the app.
2Grant permissions
1Add Bot Token Scopes
In the app settings sidebar, open OAuth & Permissions, scroll to Bot Token Scopes, and add each of the following. Each one unlocks exactly one piece of what OneClik does in Slack — nothing here is a blanket permission.
| Scope | What it's for | |
|---|---|---|
| chat:write | Post the issue message itself. | Required |
| chat:write.public | Post to a public channel without being invited to it first. | Required |
| files:write | Upload screenshots and recordings attached to the issue. | Required |
| channels:read | List public channels in the channel picker. | Required |
| groups:read | List private channels in the channel picker. | Required |
3Install & get the token
1Install to your workspace
Still on the OAuth & Permissions page, scroll up and click Install to Workspace, then approve the permissions on the confirmation screen.
2Copy the Bot User OAuth Token
After installing, the same page shows a token starting with xoxb-. Copy it now — you'll paste it into OneClik in the next phase, and you won't need to come back here unless you add a scope later.
4Connect in OneClik
1Open the Slack integration settings
In OneClik, go to Settings → Integrations → Slack and paste the bot token from Phase 3.
2Pick a channel from the dropdown
As soon as the token validates, OneClik asks Slack which channels the app can see and fills the dropdown automatically — nothing to type or look up by hand. Each channel shows whether it's private and whether the app has joined it yet:
A channel marked not joined needs an invite before you pick it — see Phase 4, step 3. Picking it anyway is fine for a public channel (messages still arrive), but every private channel needs the invite first, with no exception.
Don't see the channel you want? Type its channel ID directly instead — open the channel in Slack, choose View channel details, and copy the ID at the bottom of that panel.
3Invite the app to the channel
In Slack, open the channel you picked and type:
/invite @OneClikreplacing @OneClik with whatever you named the app in Phase 1. This step is mandatory for a private channel and strongly recommended for a public one — without it, issue text still posts, but every screenshot and recording silently fails to upload.
4Save the connection
Back in OneClik, select Connect. The token and channel are verified against Slack before anything is saved, so a typo or a revoked token is caught immediately rather than at the first real push.
Verify it worked
✓Check the connection status
The Slack settings page shows a live status pulled straight from Slack — the connected workspace name, the target channel, and any membership warning, checked fresh on every visit rather than trusted from what was saved.
2Send a test issue
Push any existing OneClik issue to Slack — with an attached screenshot, if you have one — and confirm both the message and the image land in the channel.
Troubleshooting
The message arrives but attachments never show up
This is almost always a missing invite. A public channel receives text without membership, but Slack requires the app to actually be a member of a channel — public or private — before it can share a file into it. Run /invite @OneClik in the channel and resend.
My private channel isn't showing anything at all
Private channels get nothing — not even the message — until the app is a member. Invite it with /invite @OneClik inside that channel; there's no scope or setting that lets a private channel skip this.
The channel dropdown is empty or missing channels
The token is valid but missing a read scope. Add channels:read for public channels and groups:read for private ones under OAuth & Permissions, reinstall the app, then reopen the connection form. As a fallback, paste the channel ID directly instead of using the dropdown.
Slack rejected the token when I tried to connect
The token was likely revoked or copied incorrectly. Go back to api.slack.com/apps → your app → OAuth & Permissions and copy the Bot User OAuth Token again — it always starts with xoxb-, never xoxp-.
OneClik · Integrations documentation. Need help? Contact support