outpost

Hookdeck Outpost — open-source infrastructure for sending webhooks and events to user-preferred destinations (HTTP, SQS, RabbitMQ, Pub/Sub, EventBridge, Kafka). Use when building a SaaS platform that needs to deliver events to customers.

Aller à l'installation Vérifier les fichiers

Dépôt: hookdeck/webhook-skills
Dernière activité de la source: 22 février 2026 à 17:00
Langue détectée de SKILL.md: anglais
Étoiles: 89
Forks: 14

Options d'installation

Le prompt qui vérifie d'abord la source est sélectionné par défaut. Vous pouvez passer à une commande directe ou télécharger une copie locale.

Installer avec un assistant IA

Copiez ce prompt dans l’assistant IA que vous utilisez.

Follow https://skillsmp.com/skill-install/prompt.md to install only the Agent Skill at https://github.com/hookdeck/webhook-skills/tree/main/skills/outpost.

Une commande directe contourne le prompt de vérification. Examinez la source avant de l'exécuter.

npx skills add https://github.com/hookdeck/webhook-skills --skill outpost

La commande reste sur une seule ligne. Faites défiler horizontalement pour la vérifier avant de la copier.

Vous préférez une copie locale ? Téléchargez les fichiers actuellement disponibles dans SkillsMP.

Vérifiez les fichiers source

Lisez SKILL.md et les fichiers associés affichés par SkillsMP avant de décider de l'installer.

SKILL.md

Instructions source · Aperçu en lecture seule

name: outpost
description: Hookdeck Outpost — open-source infrastructure for sending webhooks and events to user-preferred destinations (HTTP, SQS, RabbitMQ, Pub/Sub, EventBridge, Kafka). Use when building a SaaS platform that needs to deliver events to customers.
license: MIT
metadata: {"author":"hookdeck","version":"0.1.0","repository":"https://github.com/hookdeck/webhook-skills"}

# Hookdeck Outpost Outpost is open-source infrastructure for delivering events to user-preferred destinations: Webhooks (HTTP), SQS, RabbitMQ, Pub/Sub, EventBridge, Kafka, and more. Apache 2.0 licensed, available as managed by Hookdeck or self-hosted. ## When to Use Outpost - You're building a SaaS or API platform and need to send webhooks to your users - You need multi-destination support beyond HTTP webhooks (SQS, RabbitMQ, Pub/Sub, EventBridge, Kafka) - You want self-hostable webhook delivery infrastructure - You need multi-tenant support with per-user observability - You want to offer your customers reliable, retryable event delivery ## Quick Start ### Managed (Hookdeck) The fastest way to get started — Hookdeck hosts and operates Outpost for you: 1. Sign up at [hookdeck.com](https://hookdeck.com) 2. See the [Send Webhooks quickstart](https://hookdeck.com/docs/use-cases/send-webhooks/quickstart) ### Self-Hosted Run Outpost on your own infrastructure: 1. See the [Outpost documentation](https://outpost.hookdeck.com/docs) 2. Clone from [GitHub](https://github.com/hookdeck/outpost) ## Supported Destinations | Destination | Protocol | |-------------|----------| | Webhooks | HTTP/HTTPS | | Amazon SQS | AWS SQS | | RabbitMQ | AMQP | | Google Pub/Sub | gRPC | | Amazon EventBridge | AWS EventBridge | | Apache Kafka | Kafka protocol | ## Full Product Skills For detailed Outpost skills: ```bash npx skills add hookdeck/agent-skills --skill outpost ``` See [hookdeck/agent-skills](https://github.com/hookdeck/agent-skills) for the complete Outpost skill, the [Outpost documentation](https://outpost.hookdeck.com/docs), and the [GitHub repo](https://github.com/hookdeck/outpost). ## Resources - [Outpost Documentation](https://outpost.hookdeck.com/docs) - [GitHub Repository](https://github.com/hookdeck/outpost) - [Hookdeck Send Webhooks Guide](https://hookdeck.com/docs/use-cases/send-webhooks) ## Related Skills - [hookdeck-event-gateway](https://github.com/hookdeck/webhook-skills/tree/main/skills/hookdeck-event-gateway) - For receiving and ingesting webhooks (the inbound counterpart) - [hookdeck-event-gateway-webhooks](https://github.com/hookdeck/webhook-skills/tree/main/skills/hookdeck-event-gateway-webhooks) - Verify Hookdeck signatures on forwarded webhooks - [webhook-handler-patterns](https://github.com/hookdeck/webhook-skills/tree/main/skills/webhook-handler-patterns) - Handler sequence, idempotency, error handling, retry logic

Voir sur GitHub

Retour à la recherche Retour à l’installation

sentry-webhooks

Receive and verify Sentry webhooks (sentry.io — the error-monitoring and application-performance platform). Use when setting up a Sentry Integration Platform webhook handler for an internal or public integration, debugging Sentry-Hook-Signature verification, or handling events like issue.created, issue.resolved, event_alert.triggered, metric_alert.critical, error.created, comment.created, seer.pr_created or preprod_artifact.size_analysis_completed. Sentry signs with HMAC-SHA256 over the RAW body, lowercase hex, keyed with the integration's Client Secret, and sends the digest as Sentry-Hook-Signature (or Sentry-App-Signature on UI-component requests). The resource is only in the Sentry-Hook-Resource header — the body has no event/type field. Not Sentry Insurance (sentry.com), not @sentry/* SDK event ingest.

2026-10-02

pagerduty-webhooks

Receive and verify PagerDuty V3 webhooks (outbound webhook subscriptions created via the /webhook_subscriptions REST API). Use when setting up a PagerDuty webhook handler, debugging X-PagerDuty-Signature verification, or handling events like incident.triggered, incident.acknowledged, incident.resolved, incident.reassigned, incident.priority_updated, incident.annotated, incident.responder.added or service.updated. PagerDuty signs with HMAC-SHA256 over the RAW body, lowercase hex (Base16), in the X-PagerDuty-Signature header, which can carry MULTIPLE comma-separated `v1=` signatures for zero-downtime secret rotation. There is no timestamp and no replay window. Not PagerDuty Events API v1/v2 (that is inbound to PagerDuty), not V1/V2 webhook extensions, not PagerTree, not Pagerly, not Opsgenie, not incident.io.

2026-10-02

polytomic-webhooks

Receive and authenticate Polytomic webhooks. Use when building a Polytomic Webhook *destination* receiver, because Polytomic does NOT sign its payloads — there is NO signature, NO HMAC and NO signing secret, and the only authentication is a static shared bearer token compared against the connection Secret. Use when the `Polytomic-Signature-Timestamp` header misleads you into writing an HMAC verifier (it carries only an RFC 3339 timestamp, not a digest), when handling the single `sync.records` event, when looping over the `object.records[]` batch and its `hash` / user-defined `fields` keys, when deciding what `object.metadata` may be, or when a non-2xx response makes a Polytomic Model Sync appear as a failure.

2026-10-02

Tout voir dans ce dépôt

outpost

Informations de source

Options d'installation

Installer avec un assistant IA

Vérifiez les fichiers source

Plus depuis ce dépôt

Installer avec un assistant IA

Plus depuis ce dépôt