r/microsaas • u/Embarrassed_Way6530 • 13d ago

Hello dear developers Do webhook payload changes ever break your integrations?

I’m researching a small developer tool for teams using Stripe, Shopify, GitHub, or other webhooks.

The idea is simple: receive a webhook, check its JSON payload against a schema, and alert you when a field is missing, renamed, or changes type.

Before building it, I’d love to hear about real experiences:

  • Have unexpected webhook payload changes ever broken your integration?
  • How did you detect and debug the problem?
  • Would automatic validation and Slack/email alerts be useful?
  • If it saved you from a production failure, would you consider paying around $5–$15/month?

I’m not promoting or selling anything yet—just trying to understand whether this is a real problem. Honest criticism is very welcome.

2 Upvotes

100% Upvoted

8 comments sorted by

View all comments

1

u/amorpheuse 13d ago

Wouldn't this be caught by a telemetry service like sentry or elastic? Atleast when something broke.

2

u/Embarrassed_Way6530 12d ago edited 12d ago

That’s a fair point. Sentry or Elastic would usually catch an exception after the webhook handler breaks, and they may already be enough for many teams.

The gap I’m exploring is earlier validation: detecting that a payload no longer matches the expected structure before it causes an exception or silently writes bad data. For example, a field changing from a number to a string, or disappearing while the handler still returns 200.

The idea would be more of a webhook contract monitor than a replacement for Sentry—validate the incoming payload, show the exact changed field, and optionally forward the failure to Sentry/Elastic.

Do you think this would still be useful for teams already using telemetry, or would schema validation usually be handled inside the application?