Captures inbound HTTP webhook deliveries and stores payloads for inspection and automation workflows.
npx skills add https://github.com/myapihq/myapi --skill my-webhook-api
Please help me install this Agent Skill. Skill: my-webhook-api Source: https://github.com/myapihq/myapi/tree/main/skills/my-webhook-api Command: npx skills add https://github.com/myapihq/myapi --skill my-webhook-api
This Skill solves the challenge of receiving external service events reliably by providing dedicated inbound webhook endpoints that capture and store incoming deliveries for later inspection and automation.
Create a webhook endpoint and use it to receive and inspect incoming events from an external service.
High-intent search queries and answers about installing and using this skill.
To capture and inspect inbound webhooks, create a dedicated HTTP endpoint to receive external event deliveries, then store the request payloads and headers for later inspection. This allows you to review individual deliveries from services like Stripe or GitHub.
Yes, webhook endpoints can be created for third-party services like Stripe, GitHub, and Slack. You create unique endpoints for each external service to capture incoming event deliveries and store payloads for integration and inspection.
You can trigger automated workflows by binding received webhook events to your automated processes. After inbound HTTP deliveries are captured and payloads are stored, connect the received events to follow-up actions for event-driven automation.
The best way to store HTTP webhook payloads for inspection is to use a dedicated endpoint that persists incoming request bodies and headers. This enables reliable delivery lookup and review of individual event payloads from external applications.
No dependencies are required to receive external webhook deliveries. The system provides dedicated inbound HTTP endpoints natively, allowing you to capture, store, and inspect event payloads from third-party services without additional components.
When using dedicated endpoints for event ingestion, the primary limitation is that incoming deliveries are captured and stored for inspection rather than processed inline. Follow-up actions require explicit workflow binding to automate responses to the stored payloads.
webmaxruAutomate Enonic XP content lifecycle integrations via outbound webhooks and inbound HTTP endpoints.
whichguySubscribe to webhook events and trigger automated Hermes agent runs.
SystemTceIntegrate external APIs and MCP-enabled tools with Dify workflows.
myapihqAutomate webhook-triggered actions with ordered steps and payload templating.
