← Void · A-to-Mind · Fix an automation

Zapier 422 Unprocessable Entity: the app refused the data your Zap sent

You see: 422 Unprocessable Entity

What it means

The app received the request but rejected the data in it: a required field was empty, or a value was in the wrong shape (a date the app cannot read, text where it wants a number, an email that is not an email).

How to fix it

  1. Open the errored run in Zap history and look at the data the failing step sent. The empty or odd-looking field is usually visible right there.
  2. Make sure every field the app requires is mapped, and that earlier steps actually produce a value for it on every run (one blank form answer is enough to break it).
  3. Convert values to the shape the app wants with a Formatter step: dates to the format it expects, text to numbers, phone numbers cleaned up.
  4. Test the step again with a real record, then replay the failed runs.

If it keeps coming back

When only some runs fail, compare a run that worked with one that failed: the difference in their input is the cause.

Still stuck? Ask Void, free

Paste the error and what the automation does. Void names the likely cause and the fix, in seconds, no account.

Ask Void about this error

Or have it fixed: $25

One broken automation, diagnosed and repaired, with proof it runs again. Reply to the receipt with what stopped.

Get the One-Time Fix

The One-Time Fix covers one workflow. What you send and what you get back.

Sources