Slack Activities
Use the Slack group to read users and conversations from a Slack workspace, search messages, and post messages to channels.
The activities are built on the REST Client and call
https://slack.com/api. The endpoint and method are prefilled; you supply the parameters
the endpoint takes.
Available activities
Users
| Activity | Purpose |
|---|---|
| ListUsers | Lists the users in a workspace |
| GetUserInfo | Retrieves information about a user |
| GetUserProfile | Retrieves a user's profile |
| GetUserPresence | Retrieves a user's presence |
| LookupUserByEmail | Finds a user by email address |
Conversations
| Activity | Purpose |
|---|---|
| ListConversations | Lists the conversations in a workspace |
| GetUsersConversations | Lists the conversations a user belongs to |
Messages
| Activity | Purpose |
|---|---|
| SearchMessages | Searches messages in a workspace |
Connection resource
| Resource | Purpose |
|---|---|
| SlackResource | OAuth connection holding Slack credentials |
SlackResource is a resource rather than a workflow step, so it has no reference page of
its own.
Activities not yet documented
Five activities in this group — CreateConversation, InviteUsersToChannel,
OpenConversations, PostChatMeMessage and PostMessageToChannel — ship with no
configuration fields of their own and no described response fields. Everything they send
travels through the generic Target mapping, whose shape the activity configuration does
not state, so a reference page for them could not say more than that. They are left
undocumented rather than given a page that says nothing.
Authentication
Auth Type is not uniform across this group. Three shapes ship:
| Auth Type options | Activities |
|---|---|
| No Auth, OAuth 2 | GetUserInfo, GetUsersConversations, ListConversations, SearchMessages |
| No Auth, Basic, API Key, OAuth 2 | GetUserPresence, GetUserProfile, ListUsers, LookupUserByEmail |
Only GetUserInfo sets a default (OAuth 2); the rest ship with none selected.
The Auth Type help text reads "Options: No Auth, Basic, API Key, OAuth 2" on every activity, including the ones that offer only two of those. The help text is inherited from the REST Client the activities are built on.