Power Automate · Cloud flows: connector and api errors

BadRequest (400)

Short answer

BadRequest (400) in a Power Automate cloud flow: The connector API rejected the request because the input data is malformed or invalid. The most likely fix is to validate input data format.

VerifiedLast verified

01Error text

Power Automate error
BadRequest
400

02Likely causes

  • Sending a field with the wrong data type (string instead of number, or vice versa)
  • Required fields missing from the request body
  • Invalid characters in file names or list item titles
  • Exceeding a field length limit (for example, SharePoint single-line text = 255 chars)

03How to fix it

  1. Open the failed action in run history and look at the Inputs section to display exactly what was sent.
  2. Compare the inputs to the API's expected schema (check the connector documentation).
  3. Sanitize user input with replace() to strip invalid characters before passing to the action.
  4. Use substring() or take() to truncate long values to the field's max length.

04Official documentation

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

More for Power Automate work:Open Power Automate jobs

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.