DOCUMENTATION

Connect Slack to Your Playbooks

Henneth sends messages to your Slack channels via incoming webhooks, so your team gets real-time alerts and reports from playbook actions. This guide walks you through creating a Slack incoming webhook and connecting it to Henneth. Setup takes about 5 minutes.

Prerequisites

  • A Slack workspace where you have permission to install apps (or can request installation from a workspace admin)
  • The Slack channel(s) you want Henneth to post to
  • Access to your Henneth dashboard (Enterprise plan)
1

Create an incoming webhook in Slack

Go to the Slack API page for incoming webhooks and follow Slack's guide to create a new app with an incoming webhook:

  1. 1.Create a new Slack app (or use an existing one) at api.slack.com/apps
  2. 2.Navigate to Incoming Webhooks in the left sidebar and toggle it On
  3. 3.Click Add New Webhook to Workspace
  4. 4.Select the channel you want Henneth to post to (e.g., #marketing-alerts)
  5. 5.Click Allow

Slack will generate a webhook URL that looks like:

https://hooks.slack.com/services/T00000000/B00000000/XXXXXXXXXXXXXXXXXXXXXXXX

Copy this URL. You'll need it in Step 2.

One webhook per channel

Each webhook URL is tied to a specific Slack channel. If you want Henneth to post to multiple channels, create a separate webhook for each — or use the Channel Override feature in Step 2.

2

Add the connection in Henneth

Log in to your Henneth dashboard and navigate to Settings → Integrations.

Scroll to the Connections section and find Slack with the description: "Send messages to Slack channels via incoming webhooks."

Click + Add Connection and fill in the following fields:

Connection NameRequired
A friendly label for this connection (e.g., "Marketing Channel", "SEO Alerts")
Webhook URLRequired
The incoming webhook URL from Step 1
Channel OverrideOptional
Override the webhook's default channel (e.g., #general). Leave empty to use the channel you selected when creating the webhook.
Bot NameOptional
The display name for messages (defaults to "Henneth Bot")
Icon EmojiOptional
The emoji displayed as the bot's avatar (defaults to :robot_face:)
3

Test and save

Click Test Connection to send a test message to your Slack channel. Check your Slack workspace — you should see a test message from Henneth in the target channel.

If the test succeeds, click Save to store the connection.

If the test fails, verify that:

  • The webhook URL is correct and complete
  • The Slack app is still installed in your workspace
  • The target channel still exists and hasn't been archived
4

Use Slack in playbooks

Once saved, your Slack connection is available as a destination in Henneth playbooks. You can configure playbook actions to:

  • Send alertswhen AI visibility scores change significantly
  • Post reportswith periodic performance summaries to a channel
  • Notify your teamwhen new AI agent crawl patterns are detected
  • Trigger notificationsbased on audit findings or content recommendations

Each playbook action lets you select which Slack connection to use, so you can route different types of messages to different channels.

Managing connections

Multiple connections — You can create as many Slack connections as you need. Each connection points to a different webhook URL and can target a different channel.

Editing — Click on an existing connection to update its name, webhook URL, channel override, bot name, or icon emoji.

Deleting — Click the delete icon next to a connection to remove it. Any playbooks using that connection will need to be updated with a new destination.

Security best practices

Webhook URL confidentiality

Treat your Slack webhook URL like a password. Anyone with the URL can post messages to your channel. Do not commit it to public repositories or share it in public channels.

Workspace app management

Regularly review installed apps in your Slack workspace at Settings & administration → Manage apps. Remove any Henneth-related apps you no longer use.

Channel access

Consider using a dedicated channel for Henneth notifications rather than posting to general-purpose channels. This makes it easier to manage permissions and audit message history.

Credential storage

Webhook URLs are encrypted at rest using AES-256 encryption in Henneth. They are never logged in plaintext and are only decrypted when sending messages to Slack on your behalf.

Next steps

  • Permissions — understand exactly what Henneth can and cannot access
  • Troubleshooting — fix common issues with webhook delivery and message formatting