# Slack

## What this integration can do

Slack commonly serves as:

* A destination for notifications and summaries
* A source of conversational or event-driven activity
* A place where teams verify the visible result of a Protege
* A team chat surface for Proteges that receive or respond to messages

## Prerequisites

* 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

## Connect

1. Open **Integrations**.
2. Select **Slack**.
3. Complete the connection flow.
4. Confirm the integration shows as connected.

## 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

## Tool Access

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

Examples:

* Post a message
* Send a summary
* Deliver a reminder to a chosen destination

## Chat setup

Slack chat setup is team-scoped. Confirm the channel boundary before enabling a Protege that responds to Slack messages.

If Slack is disconnected or repaired, revisit any Proteges that depend on Slack chat or Slack posting.

## Permissions and scopes

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 mistakes

* 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

## Troubleshooting

* If Slack should start the Protege but no event appears, review Trigger Access and the selected source.
* If the Protege runs but no Slack output appears, review Tool Access and the destination details.
* If behavior is noisy, narrow the workflow to one destination or one event path.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.tryprotege.com/integrations/slack.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.