Prevent Webhook Timeouts with AnyHook Relay
Webhook senders like Slack and GitHub stop retrying or disabling subscriptions due to LLM call timeouts, ensuring reliable event processing without manual intervention.
How it works
The agent identifies that webhook senders have strict timeout limits (e.g., Slack 3s, GitHub 10s) which are often exceeded by LLM calls. It configures AnyHook as a relay to answer the sender immediately (200 OK) and then processes the LLM call asynchronously. This prevents the sender from hanging up, retrying excessively, or deleting the webhook subscription. The agent verifies the setup ensures the relay holds the event for up to 60 seconds, allowing the LLM to complete without affecting the sender's timeout clock.
Prompt
Paste this into an agent that has the servers below connected. Adjust the names and dates to your own.
Configure AnyHook to act as a relay for my webhook handlers that call LLMs. I need to prevent senders like Slack and GitHub from timing out and disabling my webhooks. Set up the relay to answer the sender immediately and process the LLM call in the background with retries.MCP servers it needs
Source
The vendor page this playbook is drawn from, and the passage that supports it.
A relay is the queue you do not write: AnyHook answers the sender in about a second and gives your handler 60 seconds on Free, with retriesWebhook Handler Calls an LLM and Times Out: The Fix | AnyHook