Workato · Connected app response

400 Bad Request

Short answer

A 400 Bad Request error in Workato means the external server could not process the request because it is malformed or invalid. Check field names, required values, record IDs and file sizes in the failing step, then reconnect the app.

VerifiedLast verified

01Error text

Workato error
400 Bad Request

02Likely causes

  • Field or column names are improperly formatted.
  • Required input fields are empty or contain invalid values.
  • The request uses an invalid record ID.
  • A file exceeds the external app's size limits.

03How to fix it

  1. Check that field and column names match the format the app expects, including case sensitivity and naming conventions such as snake case or camel case.
  2. Confirm that record IDs are correct and that every required field is populated.
  3. If the step uploads a file, check that the file meets the receiving service's quotas.
  4. Reconnect the app so the request uses a valid, current authentication token.
  5. If the error persists, contact Workato support.

iNotes

This error can occur in HTTP connector actions, custom connectors and app-specific actions.

04Official documentation

Test every fix in a non-production environment before you apply it to production. See how entries are verified.

More for Workato work:Open Workato jobsWorkato rates and salariesHire a senior Workato developer

The iPaaS Brief

Subscribe to The iPaaS Brief.

The iPaaS newsletter for the people who run integrations. From iPaaS Group.

Free. You finish on theipaasbrief.com and confirm by email.