Skip to main content
The Slack integration connects a workspace. Reliant acts as a bot, not as you: messages it posts come from the Reliant bot user, and your own Slack identity is never stored. You connect by installing the Reliant app in the workspace through Slack’s consent screen.

Add the bot to a channel

The bot can read and post only where it is a member. Invite it from the channel with /invite @Reliant. Posting to a channel it is not in fails with a “not in channel” error that says so, and event triggers only fire for conversations the bot is in.

Actions

Channels are identified by id (like C0123ABCD), not by name; use conversations.list to find one. A message’s ts identifies it, and replying in its thread means passing that value as thread_ts.

Events

Messages posted by bots, including Reliant’s own, never fire, so a workflow that posts cannot trigger itself. Edits and deletions do not fire either. You can match on channel, user, thread_ts and (for messages) channel_type and subtype; for reactions, reaction (the emoji name without colons) and item_user. An attribute Slack leaves out is the empty string.

Example: answer when the bot is mentioned

An event reaches a trigger only through a Slack connection to the same workspace it came from.