Hookdeck

One tenant sends 30M webhooks in five minutes. Every other tenant's events back up behind it. If you fan out webhooks for multiple customers, you've seen your own version of this. Your options today: wait it out, kill the noisy tenant, or build per-tenant queueing yourself. Delivery Groups are a fourth option. Set a key on any field in your payload, set a rate, and each tenant gets their own queue. → Define keys from body, headers, query, or path → Per-group overrides to boost VIPs or throttle greedy tenants → Per-tenant queue depth, throughput, and backlog alerts It sits on top of your existing destination rate limits, opt-in per destination. Now in early access. Request access: https://lnkd.in/eQxBFXPs

Hookdeck is sponsoring the Cowboy Corral, the dotdev after-party for the Shopify partner community. Hosted by Partner Meetup and Smarterships during Shopify Editions, it's a night for the agencies, partners, and Shopifolk building the platform. Paris Texas, Toronto, the evening of July 21, 8PM till late. Dress code is Canadian Tuxedo, so denim on denim. Supporting this community matters to us. The people in that room are shaping how Shopify stores handle events, and that's the work we care about with Outpost and Event Gateway. We'll also be at DotDev across July 21-22. Find us on the floor, then join us at the Corral. RSVP: https://lnkd.in/eRGBVyzn

🆕 Webhooks by Example - a new hands-on series. We sat down with Jeff Everhart from Knock to walk through how they use Orb's usage threshold webhooks to power customer-facing upgrade nudges. Knock uses Knock itself to send these messages - 12 distinct scenarios across plans, metrics, and thresholds, with their growth marketer editing the copy. The walkthrough covers: - Orb webhook to enrichment to 12-scenario message matrix to Postmark - Local dev with mocked payloads and sandbox mode - Dev-to-prod promotion with diffs and environment isolation Watch Episode 1: https://lnkd.in/gMeQiWpU Read the writeup: https://lnkd.in/gvJv6evP

Some Shopify app devs drop 95% of the webhooks they receive. Last week Shopify announced their solution - it's the biggest change to their webhooks in a decade. We got Taylor Page (co-founder of Shop Dev Alliance and host of Liquid Weekly), Jordan Finneran (founder of Pimsical and organizer of Shopify North), and Sandesh Kulai (founder of STOQ, a Shopify Dev Awards-winning app) on a call to get their reactions. Here's what is changing and what it means for you: Next Gen Events, currently in developer preview, flips the typical webhook subscription model. You declare: — what happened (action) — the conditions you care about (trigger) — the GraphQL shape you want delivered (query) It's a key change because as Sandesh says, "Half of our AWS bill is just consuming webhooks. If Shopify is telling me I can bring that down by 50–75%... that's like somebody giving me money for free." With the planned new setup, webhook payloads now live in the same schema universe as the GraphQL Admin API. No more translation layers between two shapes of the same data. Years of duplicated ecosystem code, gone. But the complexity doesn't disappear. It moves. "You're trading complexity for complexity. With webhooks you either scale up, use a tool like Hookdeck to dedupe, or build the logic yourself. You're just choosing where to put it," says Jordan. Plus, there's an open question around reliability. Filtering reduces volume. It doesn't change delivery guarantees. So reconciliation loops may not be going away just yet. Regardless, "Day one, we're in" says Sandy. "It's a very easy yes. The teams tried it out and the feedback is that it's ready to go..." It will also be interesting to see what impact this change has on the wider industry. Stripe quietly stopped calling them webhooks two years ago. Shopify is doing the same now — Next Generation Events, not webhooks. Check out the full session 👉 https://lnkd.in/e2eHR3gh Thanks to Taylor, Jordan, and Sandesh for joining us.

Let's talk all about Shopify new Event Subscriptions with Taylor Page, sandesh, and Jordan F.

Hookdeck Outpost GA, Better Stack integration, Outpost operator events, and new source types. Here's what shipped recently in Hookdeck: 🆕 Hookdeck Outpost is now generally available: Outpost adds webhook and event delivery to your API, SaaS, or PaaS. 🆕 Better Stack Uptime Integration: Webhook issues in Event Gateway now open incidents in Better Stack with our new integration for Uptime. 🆕 Operator Events to Outpost: They provide a structured way to subscribe to deployment lifecycle signals from your Outpost instance. 9️⃣ New Source Types: Event Gateway's verified source coverage now includes Ashby, Neon, Paystack, Paymob, Scrapfly, FireFlies, WeChat Pay, Alchemy, and GreenDot.

🎟️ For the Shopify devs: Win a free ticket to Techtonic on July 23rd in Toronto. We've teamed up with ShopDev Alliance to give away 10 free tickets to Techtonic. Fill in your details by May 15th for a chance to win → https://lnkd.in/eBb2aXPK

You can't do anything about a webhook provider's outage. But the recovery surge: that's a webhook failure mode worth planning for https://lnkd.in/eUMczADa

🆕 Webhook issues now open incidents in Better Stack Uptime When Hookdeck detects an issue with your webhooks, an incident is automatically created in Better Stack Uptime. As the issue moves through acknowledgement, updates, and resolution, the incident stays in lockstep. Resolve the incident in Better Stack, and the change flows back to Hookdeck — no more state drift between your incident tool and your webhook infrastructure. It joins Slack, Discord, and PagerDuty in our issue notification integrations.

With Outpost we wanted to make it possible to send webhooks in minutes. Here's what integrating Outpost looks like end-to-end. With a few lines of code you get reliable, observable webhook delivery to your customers.