Integration · Slack

Verified Slack webhooks for your AI agent.

Slack signing secret verification runs before persistence. Hooksbase also answers Slack `url_verification` challenges inline — no delivery is persisted for challenges, so setup stays clean.

Start freeProvider verification guide

Verification + metadata

What your agent receives

// Hooksbase verifies X-Slack-Signature + X-Slack-Request-Timestamp
// URL verification challenges handled inline (no delivery stored)
// Your agent receives:
{
  "provider": {
    "name": "slack",
    "sourceId": "event-id-...",
    "eventType": "message",
    "verified": true
  },
  "payload": { /* raw Slack event */ }
}

Routable metadata fields

Match on provider fields

Once Slackverification is enabled, these fields are available to routing rules, delivery search, and your agent's payload.

  • provider.name = "slack"
  • provider.sourceId = event_id from Slack event envelope
  • provider.eventType = e.g. "message", "app_mention"
  • provider.verified = boolean

Agent recipes

Common Slack + agent patterns

Channel triage agent

Route `app_mention` in specific channels to an agent that answers common questions or escalates to a human.

DM responder agent

Route direct-message events to a customer-support agent that handles Tier-1 inquiries from the Slack customer channel.

Workflow trigger via slash command

Slash commands land as events — agent kicks off a longer-running workflow and posts the result back to Slack.

Get started

Point Slack at Hooksbase.

Configure the Slack provider pack on a Hooksbase webhook, copy the ingest URL, paste it into your Slack webhook settings. Every verified event lands with full provider metadata on the delivery.

Start freeRead the verification guide