Webhook JSON checker
Validate payload JSON and required keys before you wire an agent trigger.
Confirm payload shape before the trigger goes live
Broken JSON or missing keys are a common reason agent triggers fail. Paste a sample payload and the keys your workflow expects to validate before wiring production.
How to use the webhook JSON checker
Paste the JSON body and a comma-separated list of required top-level keys. Fix parse errors or missing keys in the producer, then re-check.
Payload and required keys
What the result means
Valid JSON with all required keys is ready to map into the workflow. Failures need a producer fix, a field map, or a HITL path — not endless retries.
FAQ
What does the webhook JSON checker validate?
It parses the payload as JSON (the format defined by RFC 8259) and checks that each required key you list is present on the top-level object. It does not call a remote webhook or validate nested schemas beyond top-level keys.
What is RFC 8259?
RFC 8259 is the IETF standards-track document “The JavaScript Object Notation (JSON) Data Interchange Format” (December 2017). It defines valid JSON text. This checker uses the browser’s JSON.parse, which rejects text that is not valid JSON.
Why check required keys before wiring an agent trigger?
Agent and workflow triggers often assume fields like event or email exist. Missing keys cause silent skips or bad writes. Confirm the payload shape with a sample before the live endpoint is connected.
Does invalid JSON always mean a bad webhook?
Not always — some providers send form-encoded or multipart bodies. If JSON.parse fails, confirm the Content-Type and whether the body is actually JSON. If keys are missing, fix the producer or map alternate field names in the workflow.
How should retries work when a webhook payload fails validation?
Do not retry forever on schema failures — those will not clear without a change. Use exponential backoff for transient transport errors, and route persistent validation failures to a human or dead-letter queue.
Need reliable webhook-triggered agentic workflows?
GoWith agentic builds validate payloads, retry transport errors, and escalate schema failures. See all free tools, the retry / backoff calculator, the CRM hygiene checker, and the HITL gate picker.
Educational only. Not legal advice and not a substitute for testing the live agent. Webhook JSON checker runs in your browser — nothing is sent to your CRM unless you copy it yourself.