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
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
Open Integrations.
Select Slack.
Complete the connection flow.
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
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 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.
Last updated
Was this helpful?