Integration · Slack
Verified Slack webhooks for your AI agent.
Hooksbase verifies each Slack webhook signature before persisting the delivery, stamps queryable provider metadata (event type, source ID, verified flag) on the event, and routes it to your AI agent — no webhook plumbing to build.
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.
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
Route `app_mention` in specific channels to an agent that answers common questions or escalates to a human.
Route direct-message events to a customer-support agent that handles Tier-1 inquiries from the Slack customer channel.
Slash commands land as events — agent kicks off a longer-running workflow and posts the result back to Slack.
Frequently asked questions
- How do I verify Slack webhooks with Hooksbase?
- Add the Slack provider pack to a Hooksbase webhook and paste your Slack signing secret. Hooksbase verifies the `X-Slack-Signature` and `X-Slack-Request-Timestamp` headers before the delivery is persisted, so only authentic Slack events reach your agent.
- Does Hooksbase handle the Slack url_verification challenge?
- Yes. Hooksbase answers the Slack `url_verification` challenge inline and stores no delivery for it, so adding the ingest URL in your Slack Event Subscriptions setup just works without cluttering your delivery history.
- Which Slack event types can I route on with Hooksbase?
- Hooksbase extracts the Slack event type into `provider.eventType` (for example `message` or `app_mention`), so you can route on any Slack event type. The event envelope `event_id` is captured as `provider.sourceId`.
- Can I send Slack events to multiple destinations from Hooksbase?
- Yes. Hooksbase can route one verified Slack event to several typed destinations at once — for example a channel-triage agent over HTTP plus an event sink — each carrying the same provider metadata.
- Can I replay a Slack webhook delivery in Hooksbase?
- Yes. Hooksbase keeps 30-day delivery-detail retention and supports deterministic replay from the persisted dispatch snapshot, so you can re-deliver a verified Slack event to your agent after a fix without re-triggering it in 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.