Inspect

Slack

Start automations from new messages and reactions in Slack channels.

Add the trigger

Select Slack event under Add trigger, then configure:

  • When: Message posted or Reaction added.
  • In channels: one or more channels to watch. Workspace administrators can create a public channel by entering a new name and selecting Create.

Invite Inspect to each channel so it receives the channel's events. Events delivered only to a custom agent's dedicated Slack app do not start automations.

Conditions

Conditions narrow which events start a run. A run starts only when every condition matches; with no conditions, every event of the selected type in the selected channels starts a run.

For Message posted:

  • Message text: contains, does not contain, starts with, ends with, is, or is not a value. Matching is case-insensitive.
  • Message author: is any of or none of the listed Slack user or app IDs.
  • Author type: Person or App or bot.
  • Mentioned users: includes any, all, or none of the listed Slack user IDs.
  • Message location: Thread reply or Top-level message.

For Reaction added:

  • Reaction emoji: is any of or none of the listed emoji names, such as eyes or white_check_mark.
  • Reacting user: is any of or none of the listed Slack user IDs.
  • Message author: the author of the message that received the reaction is any of or none of the listed IDs. Reactions on messages whose author is unknown never match this condition.

Use Slack member IDs (for example U012AB3CD) and app or bot IDs (for example A012AB3CD or B012AB3CD), not display names.

What starts a run

New messages, including file shares and bot messages, start runs; edits, deletions, and other message subtypes do not. Messages and reactions from Inspect itself are ignored, so an automation that posts to a channel it watches does not trigger itself.

When several Slack triggers on one automation match the same event, the automation runs once. The same message or reaction delivered again does not create another run.

The agent receives the workspace, channel, and message timestamp. Message runs also include the thread timestamp, the sender's user, bot, or app ID, and the message text. Reaction runs include the emoji name, the reacting user, and the original message's author.

Example

To triage requests posted in #help-payments, add a Message posted trigger for that channel with Message location set to Top-level message and Author type set to Person. Write a prompt that tells Inspect how to investigate each request and where to report what it finds.