Blog

Tutorials

Tutorials are hands-on FastHook workflows. Each one starts with a real developer task and ends with a route, command, receiver behavior, or recovery operation you can inspect.

Use this section when you want practical implementation paths rather than API field lists: build the route, send traffic, verify what happened, and then harden the workflow.

Tutorial Tracks

The tutorials are organized around the lifecycle of a webhook integration. Start with ingestion, then move through local testing, provider verification, routing, and operational recovery.

  • Build: create sources, destinations, connections, and a first working delivery.
  • Test: use fasthook.exe or fasthook-cli to route provider traffic to localhost.
  • Secure: verify inbound provider signatures and outbound FastHook delivery signatures.
  • Route: fan out one provider stream to several downstream consumers.
  • Recover: retry requests or events after a failed receiver deploy.
  • Operate: control delivery pressure with pause, rate limits, retries, and bulk operations.

Start With These Workflows

  • Receive Webhooks: create a public source URL, connect it to a destination, send a test event, and inspect the resulting request, event, and attempt.
  • Test Webhooks Locally: run a local receiver, connect a CLI destination, and replay provider traffic through an authenticated tunnel.
  • Verify Webhooks: configure provider verification at the source and FastHook signing at the destination.
  • Fan-Out Webhooks: split one accepted request into multiple independent delivery branches.
  • Deduplication Patterns: choose a stable dedup key and suppress repeated deliveries on one route.
  • Control Throughput: protect slow receivers with filters, destination rate limits, pause/HOLD, retry backoff, and targeted replay.

Tutorial Shape

Every tutorial should leave you with something runnable and inspectable. The useful artifact is not just a code snippet; it is a FastHook route whose records explain what happened.

  • A concrete starting state, such as a new provider webhook or a failing destination.
  • The FastHook objects involved: source, destination, connection, rule, request, event, or attempt.
  • Commands or dashboard steps that create the workflow.
  • A test payload or provider event that proves the path works.
  • Inspection steps for Requests, Events, Attempts, Metrics, or bulk operation status.
  • A cleanup or production note so the tutorial does not leave unsafe defaults behind.

Example Learning Path

Path
1. Create a source and receive a test webhook.
2. Send the same traffic to localhost with a CLI destination.
3. Enable provider signature verification.
4. Add a second destination branch for fan-out.
5. Add deduplication for provider retries.
6. Add throughput controls before replaying a failed window.

When To Use Tutorials Instead Of Reference

  • Use tutorials when you are wiring a full workflow across multiple FastHook resources.
  • Use tutorials when the hard part is operational order: what to create first, what to test, and what to inspect.
  • Use the API reference when you already know the route and need exact request fields, response shapes, or endpoint paths.
  • Use concept docs when you need the mental model before touching production traffic.

Planned Deep Dives

  • Build a webhook receiver from zero.
  • Route Stripe billing events to a worker.
  • Debug GitHub webhook delivery with request and attempt records.
  • Replay failed events after a destination outage.
  • Ship a local-to-production webhook workflow with fasthook.exe.
  • Design idempotent receivers for retries and bulk replay.

Next