Appearance
Slack Connection
The Slack Connection authorizes a Slack workspace for supported conversation, message, user, file, and inbound-event operations.
Slack is exposed through server methods and the $io.slack API. It is not exposed as a general Connection command in the Page Flow or Cloud Flow command selector.
Capabilities
| Capability | Availability |
|---|---|
| Connection service identifier | slack |
| Page Flow commands | Not exposed |
| Cloud Flow direct commands | Not exposed in the command selector |
| Connection methods | Supported |
| Server API | $io.slack |
| Connection-backed SDK object | Not documented |
| AI Agent Connection support | Supported |
Authentication Modes
The Slack Profile supports:
| Mode | Use |
|---|---|
| OAuth2 | Authorize through the ioLoop-provided Slack OAuth application. |
| Custom Bot Token | Supply a Slack bot token directly. |
| Custom OAuth2 | Authorize through your own Slack application using its client ID, client secret, and scopes. |
For a custom bot token, provide a bot token issued for the intended workspace. For custom OAuth, configure the Slack application and its redirect URL before completing authorization.
Profile Settings
Depending on the selected mode, the Profile uses:
- Bot Token for Custom Bot Token mode.
- Client ID and Client Secret for Custom OAuth2.
- OAuth Scopes, represented as a comma-separated list, when custom scopes are required.
Slack operations can use bot or user authorization depending on the granted scopes and the documented method. Grant only the scopes required by the Project.
The Connection has no additional service fields beyond its name and selected Profile.
Server Methods
The Slack Server API includes supported operations for areas such as:
- Listing conversations and retrieving conversation information.
- Reading conversation history, members, and thread replies.
- Posting, scheduling, deleting, and linking to messages.
- Listing users and retrieving user information.
- Listing files.
- Resolving a channel by name.
- Processing supported inbound webhook information.
Use the Connection Function Call block or $io.slack for the current method names and parameter structures.
Access and Backend Design
Slack exposes an Invoke/Execute Access operation, and Public access is not allowed.
Keep Slack operations in Cloud Flow. If a Page needs to post or retrieve Slack data, call a controlled Cloud Flow Web Hook that validates the Project User and limits channels, message content, and operations.
Do not let browser input select an arbitrary Slack API path, actor, or destination without server-side validation.
Testing
Authorize a controlled workspace first. Confirm that the installed application or bot belongs to the intended workspace and has the required scopes.
Test with non-production channels and verify message identity, visibility, deletion behavior, pagination, missing scopes, and rate-limit handling.