Feat: Webhooks

[mrkaye97]

Description

Adds support for webhook-as-event, where we allow you to set up a webhook (via UI or API) and we'll handle incoming webhooks and process them as events within Hatchet as if they were published from a Hatchet SDK directly.

Example request to create a webhook:

{
    "sourceName": "STRIPE",
    "name": "stripe-test-webhook",
    "eventKeyExpression": "'stripe:' + input.type",
    "authType": "HMAC",
    "auth": {
        "algorithm": "SHA256",
        "encoding": "HEX",
        "signatureHeaderName": "Stripe-Signature",
        "signingSecret": "whsec_<snip>"
    }
}

To get events sending from Stripe, create a webhook pointing at: /api/v1/stable/tenants/< id >/webhooks/stripe-test-webhook

Misc other things:

1. On the FE, handled the Stripe / Github cases basically as wrappers of the HMAC auth option, where we pre-populate the fields we know from the Stripe / GH docs with their values instead of making the user fill them in
2. Used a built-in Echo rate limiting middleware for handling rate limiting - set to 50 base, 100 burst by default 🤷

Type of change

• New feature (non-breaking change which adds functionality)

TODO:

• Wire up writes of validation failures into a table in the OLAP DB for monitoring
• Add struct validation on creation
• Documentation
• Populator tests
• sqlc make nullable cols nullable (pgtype.Text) on insert
• order by tenant, inserted at on the list query
• maybe rm index for source name
• set env var for max webhooks per tenant
• set up partitioning like we do for other tables
• implement in-memory rate limiter

FE Screenshots:

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
hatchet-docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jul 25, 2025 9:59pm
hatchet-v0-docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jul 25, 2025 9:59pm

[mrkaye97]

wasn't sure what reasonable values here were, but 50 / 100 RPS seemed okay to start with