Ctrlk
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Slack

What this is

Slack is a Hookshot™ integration that connects your Slack workspace to Hookshot. Slack commonly serves as a destination for notifications and summaries, a source of event-driven activity, and a chat surface where Proteges can respond to messages.

When to use it

  • When a Protege should post messages or summaries to Slack

  • When Slack activity should start a Protege

  • When you want to talk to a Protege inside a Slack thread by mentioning @hookshot

What you need first

  • Access to the Slack workspace you want to connect

  • Permission to approve the Hookshot connection flow

  • A clear channel or audience boundary for the workflow

Steps

1. Connect Slack

  1. Open Integrations.

  2. Select Slack.

  3. Complete the connection flow.

  4. Confirm the integration shows as connected.

2. Review Trigger Access

Use Trigger Access when Slack should start the Protege.

Examples:

  • A channel-specific event

  • A Slack activity pattern your workspace wants to monitor

Confirm the correct trigger source is live and mapped to the intended channel boundary.

3. Review Tool Access

Use Tool Access when the Protege should do something in Slack.

Examples:

  • Send a message

  • Send a summary

  • Deliver a reminder to a chosen destination

Tool Access deserves extra review for Proteges that post messages. Grant only the posting actions the workflow needs, and confirm the destination channel is correct.

4. Set up chat

Slack chat is team-scoped. When you enable chat on Slack, Hookshot can respond to direct mentions in channels where the Slack bot is present:

  • Mention @hookshot, @hookshotdev, or @composio to invoke a response

  • Hookshot replies in the same Slack thread as the mention

  • While processing, an :eyes: emoji reaction appears on the triggering message

  • Follow-up messages in the same thread continue the conversation without needing another mention

Chat connections are always team-scoped — they cannot be personal connections.

See Chat for the full chat feature documentation.

5. Review permissions

Review the Slack consent screen carefully. In practice, Hookshot needs permission to:

  • Observe the Slack activity that should start the workflow

  • Post or update the Slack output your Protege is expected to produce

If you approve too little, the connection may look healthy while the Protege still cannot start or act correctly.

How to verify

  • Confirm Slack is connected in Integrations

  • Confirm the intended Slack trigger source is live, if Slack starts the workflow

  • Confirm Tool Access covers the posting behavior you expect

  • Confirm chat configuration is enabled if Slack messages should start the workflow

  • Confirm Event Feed shows the Slack-related event or downstream activity

  • Confirm Audit shows the run and outcome

Common failures

  • Connecting the wrong Slack workspace

  • Posting into the wrong channel boundary

  • Assuming any Slack connection can post everywhere you care about

  • Debugging only in Slack instead of checking Event Feed first

  • Enabling chat but not confirming the chat connection is active

  • Expecting Hookshot to respond without an explicit @hookshot mention

  • Using a personal connection instead of a team connection for chat

Next step

PreviousIntegrationsNextGitHub

Last updated

Was this helpful?