Hookdeck
Hookdeck is a platform that enables developers to manage, monitor, and secure webhooks and API events.
Verdict
Common use cases
- Debug failed webhook deliveries during incidents
- Bulk-retry events after downstream service recovers
- Cancel stuck retries for malformed payloads
- Inspect event payloads without opening dashboard
- Provision new webhook sources for feature launches
Integration
- Vendor
- Hookdeck
- Category
- developer-tools
- Auth
- API_KEY
- Tools
- 39
- Composio slug
hookdeck
Tools
- Bulk Cancel Hookdeck Events
Tool to create a bulk cancellation job for events. Use when you need to cancel multiple events matching filters.
- Bulk Retry Hookdeck Events
Tool to initiate a bulk retry for a set of events. Use when you need to retry multiple failed events matching filters.
- Cancel Hookdeck Event
Tool to cancel all future delivery attempts for a specific event. Use when you need to stop retries of an event before manual intervention.
- Cancel Hookdeck Scheduled Retries
Tool to cancel all future scheduled retries for an event. Use when you need to mute automatic retry attempts after repeated failures.
- Create Hookdeck Bookmark
Tool to create a new bookmark. Use when you want to bookmark a specific event for quick access.
- Create Hookdeck Connection
Tool to create a connection between a source and a destination. Use after setting up or referencing source/destination.
- Create Hookdeck Destination
Tool to create a new Hookdeck destination. Use after setting up sources when you need to route events to endpoints.
- Create Hookdeck Source
Tool to create a new Hookdeck source. Use after setting up your project when you need to receive and route incoming webhooks.
- Create Hookdeck Transformation
Tool to create a new Hookdeck transformation. Use when you need to execute custom JavaScript to modify event payloads before delivery.
- Delete Hookdeck Bookmarkdestructive
Tool to delete a specific bookmark by its ID. Use when you need to permanently remove a bookmark after confirming it's no longer needed.
- Delete Hookdeck Connectiondestructive
Tool to delete a specific connection by its ID. Use when you need to permanently remove a connection after confirming it's no longer needed.
- Delete Hookdeck Destinationdestructive
Tool to delete a specific destination by its ID. Use when you need to permanently remove a destination after confirming it's no longer needed.
- Delete Hookdeck Sourcedestructive
Tool to delete a specific source by its ID. Use when you need to permanently remove a source after confirming it's no longer needed.
- Delete Hookdeck Transformationdestructive
Tool to delete a specific transformation by its ID. Use when you need to permanently remove a transformation after confirming it's no longer needed.
- Get attempts
Tool to list delivery attempts for your Hookdeck account. Use when you need to retrieve attempt logs, filter by event ID, and paginate through results.
- Get events
Tool to list events for your Hookdeck account. Use when you need to retrieve delivery logs, filter by status or time, and paginate through results.
- Get Hookdeck Attempt
Tool to retrieve details of a specific Hookdeck attempt by its ID. Use after confirming the attempt ID.
- Get Hookdeck Connection
Tool to retrieve details of a specific Hookdeck connection. Use after confirming the connection ID.
- Get Hookdeck Destination
Tool to retrieve details of a specific Hookdeck destination. Use after confirming the destination ID.
- Get Hookdeck Request
Tool to retrieve details of a specific Hookdeck request. Use after confirming the request ID.
- Get Hookdeck Source
Tool to retrieve details of a specific Hookdeck source. Use after confirming the source ID.
- Get Hookdeck Transformation
Tool to retrieve details of a specific Hookdeck transformation. Use after confirming the transformation ID.
- Get sources
Tool to retrieve all sources associated with your Hookdeck account. Use when you need to list or filter hook sources.
- Get transformations
Tool to list Hookdeck transformations. Use when you need to retrieve or filter your Hookdeck transformations.
- Hookdeck: Get Connections
Tool to list Hookdeck connections. Use when you need to retrieve or filter your configured connections.
- Hookdeck: Get Destinations
Tool to list Hookdeck destinations. Use when you need to retrieve or filter your configured destinations.
- Hookdeck: Get Requests
Tool to list Hookdeck requests. Use when you need to retrieve requests with optional filters and pagination.
- Hookdeck: List Issues
Tool to list all issues detected in your Hookdeck account. Use when you need to retrieve and filter issues by type, status, or time.
- Hookdeck Update Connection
Tool to update an existing connection. Use when you need to modify the name, description, or rules of a connection.
- Hookdeck Update Source
Tool to update a Hookdeck source. Use when you need to modify the name, type, description, or config of an existing source.
- List Hookdeck Bookmarks
Tool to list bookmarks. Use when you need to retrieve your Hookdeck account's bookmarks with optional filters and pagination. Use after authenticating your session.
- Manually Retry Hookdeck Event
Tool to manually retry a specific Hookdeck event delivery. Use when an event has failed and you need a manual retry.
- Replay Hookdeck Event
Tool to replay a specific Hookdeck event. Use when you need to manually retry a failed event delivery.
- Resolve Hookdeck Issue
Tool to resolve a Hookdeck issue. Use after confirming the underlying issue has been addressed.
- Retrieve Hookdeck Issue
Tool to retrieve details of a specific Hookdeck issue. Use after confirming the issue ID.
- Send Hookdeck Source Request
Tool to send HTTP requests to a Hookdeck Source URL. Use when ingesting test payloads to generate events for testing HOOKDECK_GET_EVENT.
- Trigger Hookdeck Bookmark
Tool to trigger a stored request via its bookmark ID. Use when replaying the stored request associated with a bookmark.
- Update Hookdeck Destination
Tool to update an existing Hookdeck destination. Use when you need to modify a destination's settings after creation.
- Update Hookdeck Transformation
Tool to update an existing Hookdeck transformation. Use when you need to modify a transformation's code, name, or environment variables after creation.
Setup
Setup guide
- 11. In Switchy, open your workspace settings and navigate to the MCP Integrations section. 2. Click 'Add Integration' and select Hookdeck from the developer tools category. 3. Log into your Hookdeck account, go to Settings > API Keys, and generate a new key with full read-write permissions. 4. Paste the API key into Switchy's connection form and click 'Connect'. 5. Open any Space, type '@Hookdeck list sources' and send the message to confirm the connection works. 6. If you see your webhook sources listed, the integration is live — you can now query events, manage retries, and create connections directly from chat.
What teammates see: by default, memories from Hookdeck are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
List Failed Events
@Hookdeck show me all failed events from the last 24 hours. Include the event ID, source name, and error message for each.Open in a Space →
Retry Specific Event
@Hookdeck retry event evt_abc123xyz. Confirm when the retry attempt completes and show me the response status.Open in a Space →
Bulk Retry After Outage
@Hookdeck bulk retry all events from source 'stripe-webhooks' that failed between 2:00 PM and 2:30 PM today. Show me the job status.Open in a Space →
Create New Source
@Hookdeck create a new source called 'github-repo-events' with verification enabled. Give me the webhook URL to paste into GitHub.Open in a Space →
Cancel Stuck Retries
@Hookdeck cancel all scheduled retries for events matching destination 'legacy-api' and status code 400. Confirm how many retries were cancelled.Open in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@hookdeck show me all failed webhook events from the last 24 hours for our Stripe integration, grouped by error type
Based on your Hookdeck account, here's a summary of failed Stripe webhook events in the last 24 hours: **Connection Timeout (12 events)**: Your endpoint at api.example.com/webhooks/stripe took >30s to respond. Most recent: payment_intent.succeeded at 2:14 PM. **HTTP 500 (8 events)**: Internal server errors from your endpoint. Spike occurred between 11 AM - 12 PM. **HTTP 401 (3 events)**: Authentication failures, likely due to rotated webhook signing keys. All events are queued for automatic retry. The connection timeout events may need endpoint optimization or timeout adjustment in your Hookdeck destination settings.
This example showcases Hookdeck's event filtering and diagnostic capabilities. The MCP can query events by source, status, and timeframe, then surface patterns in webhook failures. Requires read access to your Hookdeck workspace. Response reflects your actual event data — empty projects will return no results.
@hookdeck bulk retry all failed payment_intent.succeeded events from the last hour that got HTTP 500 errors
Bulk retry job created successfully. **Job ID**: retry_2k4m8x9p **Matched Events**: 8 events **Filter Applied**: source=stripe, event_type=payment_intent.succeeded, status=failed, http_status=500, created_at >= 1 hour ago **Status**: Processing Hookdeck is now retrying these events against your destination endpoint. Retries will respect your connection's retry strategy (exponential backoff, max 5 attempts). You can monitor progress in the Hookdeck dashboard under Bulk Operations, or I can check status if you provide the job ID.
This demonstrates Hookdeck's bulk retry capability — essential for recovering from transient outages without manual intervention. The MCP creates the job but doesn't wait for completion; bulk operations are asynchronous. Be cautious with broad filters; you could inadvertently retry thousands of events and overwhelm your endpoint.
@hookdeck create a new connection routing GitHub webhook events from our main repo to our staging API, with a 60-second timeout and linear retry strategy
Connection created successfully: **Name**: github-main-to-staging **Source**: github-main-repo (webhook URL: https://events.hookdeck.com/e/src_abc123) **Destination**: staging-api (https://staging.example.com/webhooks/github) **Timeout**: 60 seconds **Retry Strategy**: Linear (5 attempts, 5-minute intervals) Next steps: 1. Add the source webhook URL to your GitHub repository settings (Settings > Webhooks) 2. Set the webhook secret in Hookdeck for signature verification 3. Test with a ping event from GitHub This connection will now receive all GitHub events and forward them to your staging API with automatic retries on failure.
This example shows Hookdeck's connection setup workflow, which is core to routing webhook traffic. The MCP can create sources, destinations, and connections in one flow. However, it cannot configure GitHub's side — you still need to manually add the webhook URL in GitHub's UI. The returned webhook URL is real and immediately active.
Use-case deep-dives
When Hookdeck wins for post-deploy webhook triage
A 5-person backend team ships a payment integration on Friday afternoon. By Monday morning, 200 webhook events from Stripe have failed because the new endpoint returns 503s under load. The team needs to inspect the payloads, cancel the broken retries, and replay them after the fix ships. Hookdeck's bulk retry and cancel tools let them filter by status and timestamp, stop the noise, and replay the batch in one operation. The bookmark tool flags the three edge-case payloads that need manual review. This scenario works because the team already routes webhooks through Hookdeck—if you're debugging webhooks that hit your server directly, you'd need to instrument logging first. If your team ships webhook integrations more than once a quarter, Hookdeck's replay and inspection tools pay for themselves in the first incident.
When this MCP speeds up webhook support tickets
A 3-person support team at a SaaS company gets a ticket: a customer's Shopify order webhook never triggered their fulfillment flow. The support rep needs to find the event, check if it arrived, and see why it didn't reach the destination. With Hookdeck's MCP, the rep searches events by customer ID, inspects the payload and delivery attempts, and sees the destination returned a 401. They bookmark the event, escalate to engineering, and link the bookmark in the ticket. The scenario breaks down if your support team doesn't have API key access or if webhook volume is under 100 events per day—manual dashboard lookups are faster at that scale. If your support team fields webhook questions weekly, giving them MCP access to search and bookmark events cuts median resolution time by 40%.
When Hookdeck's connection tools simplify staging
A 2-person startup is setting up a staging environment for their webhook-heavy app. They need to clone production's webhook routing—6 sources from Stripe, Twilio, and GitHub, each mapped to staging endpoints. The team uses Hookdeck's create source, create destination, and create connection tools to script the setup in 15 minutes instead of clicking through the dashboard 18 times. The MCP's tool names map directly to Hookdeck's API, so the script doubles as documentation for the next engineer. This works because the team already uses Hookdeck in production and needs reproducible staging config. If you're setting up webhook routing for the first time, the dashboard's guided flow is clearer. If your team spins up staging or preview environments more than once a month, scripting Hookdeck setup through the MCP saves 2 hours per environment.
Frequently asked
What does the Hookdeck MCP do in Switchy?
It lets your team manage webhook infrastructure without leaving the AI workspace. You can create sources and destinations, bulk retry failed events, cancel scheduled retries, and bookmark specific webhook payloads for debugging. Think of it as operational control over your webhook delivery pipeline — routing, filtering, and troubleshooting — all through natural language commands in Switchy.
Do I need admin access to connect Hookdeck?
You need a Hookdeck API key with write permissions. Hookdeck uses API_KEY authentication, not OAuth, so whoever connects it must have access to generate keys in your Hookdeck workspace settings. If your team restricts API key creation to admins, you'll need their help. Otherwise, any developer with key access can connect it.
Can the Hookdeck MCP modify webhook payloads or transform data?
No. The MCP handles operational tasks like creating connections, retrying events, and canceling deliveries. It doesn't transform payloads, apply filters at the data level, or edit webhook content. For transformations, you still configure those rules in Hookdeck's dashboard — the MCP just orchestrates the infrastructure around them.
Why use this instead of the Hookdeck dashboard?
Speed and context. If you're already troubleshooting in Switchy — reviewing logs, discussing an outage — you can bulk retry 500 failed events or cancel a runaway webhook without switching tabs. The MCP exposes 39 tools, so repetitive tasks (bookmark this event, cancel those retries) become one-line commands instead of multi-click workflows.
Who on the team should connect the Hookdeck MCP?
Whoever owns webhook reliability — usually a backend engineer or DevOps lead. They'll need access to your Hookdeck API keys and understand your event routing setup. Once connected, the whole team can query event status or retry failures, but the person connecting it should know which sources and destinations matter for your stack.