Sets up and configures Hookdeck Outpost for outbound event delivery to customer endpoints. Use when sending webhooks to customers, building webhook delivery infrastructure, managing tenants and destinations with supported types (webhooks, Hookdeck Event Gateway, AWS SQS/Kinesis/S3, Azure Service Bus, GCP Pub/Sub, RabbitMQ, Kafka), or aligning topics and publishes. EventBridge support is tracked in GitHub issues.
88
85%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Failed to scan
The risk profile of this skill
Outbound event delivery: publish platform events to tenants’ destinations (webhooks, queues, cloud buses—see supported destinations). Open source on GitHub; managed on Hookdeck Cloud or self-hosted.
Single source of truth: Use Hookdeck Outpost documentation for concepts, API, quickstarts, and UI guidance. This skill links there and adds agent workflow notes under references/.
llms.txt: https://hookdeck.com/docs/outpost/llms.txt — plain-text map of doc pages as .md URLs; fetch once when you need the full tree or many pages.https://github.com/hookdeck/outpost/blob/main/docs/apis/openapi.yamlUse the official managed-Outpost walkthroughs before opening full-stack examples in this repo:
| curl (HTTP only) | Hookdeck Outpost curl quickstart |
| TypeScript | TypeScript quickstart |
| Python | Python quickstart |
| Go | Go quickstart |
Compact link list: references/outpost-quickstarts.md.
When you need a throwaway HTTPS URL for a webhook destination (quickstarts, curl examples, “verify delivery”):
https://hkdk.events/…), and inspect or replay deliveries in one place. This is the Hookdeck-native default for agents and humans.Dashboard-style guidance (no {{PLACEHOLDERS}} — those stay dashboard-only):
BFF / wire JSON: Authentication · Wire JSON, SDK responses, and your UI
Available: Webhooks (HTTP), Hookdeck Event Gateway, AWS SQS, AWS Kinesis, AWS S3, Azure Service Bus, GCP Pub/Sub, RabbitMQ (AMQP), Kafka
Planned: AWS EventBridge
https://api.outpost.hookdeck.com/2025-07-01); verify live docs/project settings if unsure.Use only when the task needs realistic BFF + dashboard patterns—not for “smallest example” (use Quickstarts and llms.txt first).
Integration maps (read before opening trees):
Treat examples as references, not copy-paste scaffolds. Prefer the user’s codebase and use maps for Outpost-specific behavior (server-only admin key, tenant mapping, BFF routes, domain publish).
| Example | Stack | Location |
|---|---|---|
| SaaS (Next.js) | App Router + @hookdeck/outpost-sdk + dashboard UI | examples/nextjs-saas/ — README |
| SaaS (FastAPI + React) | FastAPI BFF (httpx → Outpost) + template UI | examples/fastapi-saas/ — README |
Dependency and version pins live in the example manifests (package.json, pyproject.toml).
How to use the examples: Read the integration maps and README overviews first; open other files only when they match the user’s task.
Tests: npm test in nextjs-saas (Vitest); pytest test_outpost_wire.py in fastapi-saas/backend via ./scripts/test-examples.sh outpost. Next.js example uses npm.
Destination-specific skills (outpost-webhooks, outpost-sqs, …) may be added as documentation matures.
94c610d
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.