1 read
The list of public channels.
- List channels
Protuno can list your channels, post reports and alerts, and ask for approval with a yes or no in a thread. Posts ask you first by default.
No install needed for the audit. We suggest connecting a staging copy of your site first, before your live site.
Reads can run on their own. Writes ask you first by default.
1 read
The list of public channels.
2 writes
Post a message and ask for approval. Both ask first by default.
Showing 3 of 3 capabilities
List channelsslack.channels.read
Lists the public channels in the workspace, so Protuno can find the channel to post in.
Needs: Scope: channels:read. Public channels only.
Post a messageslack.channel.post
Posts one message per run into a channel the bot has joined, for example a run summary or an alert.
Undo: Not reversible by Protuno. Delete the message in Slack if you do not want it.
Needs: Scope: chat:write. Invite the bot to the channel first. Slack allows about one post a second per channel.
Ask for approvalslack.approval.request
Posts a message that asks for a yes or no in a thread, so a person can approve a change from Slack.
Undo: Not reversible by Protuno. Delete the message in Slack if you do not want it.
Needs: Scope: chat:write. Invite the bot to the channel first.
Protuno uses Slack as a place to post run output and to ask for a yes or no. The only thing it reads is the channel list. Posts ask first by default.
Lists the public channels in the workspace, so Protuno can find the one you want its messages in.
ReadsPosts one message per run with what changed and what needs attention, instead of making the team open the dashboard.
Ask firstPosts a message that asks for a yes or no in a thread, so a person can approve a change without leaving Slack.
Ask firstNo playbook reads it yet.
How it connects: you create a Slack app in your own workspace and paste its bot token into Protuno. Protuno can only do what the app's scopes allow. Your Slack password is never shared.
Name it and pick your workspace. In the app's settings, open the permissions page and add the bot token scopes channels:read, chat:write and users:read.
you see: Your new app's settings page, with the three scopes listed under bot token scopes.
It starts with xoxb-. A workspace admin may need to approve the install.
you see: A token starting with xoxb-, shown once you install the app.
The bot can only post in channels it has joined.
you see: A line in the channel saying the app joined.
you see: A field for the token and a Connect button.
Reads run on their own. Writes ask you first by default.
you see: Reads on the left and writes on the right. Each capability is named in the form tool.resource.verb.
you see: A plain sentence summing up exactly what was granted, an Agree button and a confirmation screen.
No. The Web API methods Protuno uses (conversations.list and chat.postMessage) are available on Slack's free and paid tiers alike. Enterprise-only admin.apps.* scopes are not part of this grant.
Slack limits how fast a bot can post, about one message a second per channel. The limits can be tighter for apps outside the Slack Marketplace. Slack's rate limits page has the current numbers.
It cannot read messages or files, create channels or add people to the workspace. It lists channels and posts messages, and posting asks you first by default.
The bot must be invited to the channel before it can post there. If it was removed from the channel, re-invite it with /invite @YourAppName. This is the most common cause of a failed post.
If the workspace has app approval turned on, an owner reviews the requested scopes under Tools & settings, Manage apps, and approves or restricts them before installation completes. Admins can later restrict or require re-approval from the same screen.
In Slack, open your workspace name, then Tools & settings, Manage apps, Installed Apps. Find the app, open Configuration and choose Remove App. Disconnecting in Protuno does not revoke the key at Slack. Delete it there to cut access for good.
Capability names and default settings (on its own or ask first) are Protuno's own, and they can change as the product develops. Playbook plan, schedule and date come from Protuno's agent pages. Protuno last confirmed this connector's build status on 13 Oct 2026. Vendor limits and permissions on this page follow the vendor's public documentation as reviewed on 13 Oct 2026. The vendor's own page is the final word.
The free audit looks at the site from the outside. Connect tools afterwards, one capability at a time.
We suggest connecting a staging copy of your site first, before your live site.
That does not look like a web address. Try yourdomain.com
85 Site ChecksNo Credit Card100% Free