Slack Integration

webhook.rodeo can send webhook events directly to Slack channels, turning your webhook activity into real-time team notifications. Perfect for monitoring production events, debugging integrations, or keeping your team in the loop.

Why Slack?

Instead of logging into webhook.rodeo to check if a webhook arrived, your team gets instant Slack notifications. Common use cases:

• Production monitoring - Know immediately when critical webhooks arrive
• Team visibility - Share webhook activity across your team
• Debugging - See webhook details without leaving Slack
• Alerts - Get notified about failed deliveries
• Audit trail - Permanent record in Slack history

Connecting Slack

Before you can send webhooks to Slack, you need to connect your Slack workspace:

First-time setup

1. Navigate to Integrations in your webhook.rodeo dashboard
2. Click "Connect Slack Workspace"
3. You'll be redirected to Slack's authorization page
4. Select the workspace you want to connect
5. Click "Allow" to grant permissions

webhook.rodeo needs these Slack permissions:

• Send messages - Post webhook notifications to channels
• Read channels - List available channels for selection
• Join channels - Automatically join public channels you select

Multiple workspaces

You can connect multiple Slack workspaces to webhook.rodeo. This is useful if you:

• Have separate workspaces for staging and production
• Work with multiple teams or clients
• Want different webhooks in different workspaces

Adding a Slack destination

Once your workspace is connected, you can send webhooks to any channel:

1. Open your webhook details
2. Click "Edit"
3. Select "Slack" as the destination type
4. Choose workspace and channel
5. Click "Save"

Event formatting

When a webhook arrives, webhook.rodeo sends a beautifully formatted message to your Slack channel with details of the payload.

Message structure

🎯 Webhook Received: webhook-name

📊 Status: Delivered
🕐 Time: 2:30 PM
🆔 Request ID: req_abc123

📦 Payload (first 500 chars):
{
  "event": "purchase.completed",
  "amount": 4999,
  "customer": "cus_abc123"
  ...
}

🔗 View Full Event

Slack blocks

The message uses Slack's Block Kit for rich formatting:

• Header with webhook name
• Status badge (green for success, red for failed)
• Metadata section with timestamp and IDs
• Payload preview in a code block
• Action button linking to the full event in webhook.rodeo

Clicking "View Full Event" takes you directly to the event detail page where you can see complete headers, full payload, and delivery attempts.

Private vs public channels

Public channels

For public channels, webhook.rodeo automatically joins when you add it as a destination. You'll see:

webhook.rodeo joined #webhook-notifications

The bot sends a welcome message confirming it's ready to receive events.

Private channels

Private channels require manual invitation:

1. Add the Slack destination in webhook.rodeo
2. You'll see a warning: "This is a private channel..."
3. In Slack, type: /invite @Webhook Rodeo in the private channel
4. The bot will join and start sending events

Managing destinations

Viewing destinations

In your webhook details, the Destinations section shows:

• Connected Slack workspace(s)
• Channel name(s)
• Active status
• Last delivery time

Removing destinations

To stop sending to Slack:

1. Edit your webhook
2. Switch destination type to "None" or "URL"
3. Save

The bot will remain in the Slack channel but won't post new messages.

Reauthorizing

If your Slack token expires or is revoked:

1. Go to Integrations
2. Disconnect and reconnect your workspace
3. Edit your webhook to reselect the channel