topic Re: /automation/v4 API HTTP 400 in APIs & Integrations

/automation/v4 API HTTP 400

shubjain — Thu, 12 Jun 2025 09:31:21 GMT

Hi,

I'm trying to batch update workflows based on existing workflows in a different account.

I use the GET https://api.hubapi.com/automation/v4/flows/ID endpoint to get the JSON of a workflow, and then PUT https://api.hubapi.com/automation/v4/flows/ID endpoint to update another workflow with the same JSON (patching the revisionId and ID as needed).

This works for most of my requests, but is failing for around 50 out of 200 with the following errors:

- Invalid request to flow update (38)

- Invalid custom code action request (5)

- Existing classic flow must have classic enrollment settings (5)

The main one is the "Invalid request to flow update" - does anyone know how I can determine what is wrong with my request?

Re: /automation/v4 API HTTP 400

Jaycee_Lewis — Thu, 12 Jun 2025 19:01:19 GMT

Hey, @shubjain 👋 Welcome to our community. I couldn't find a documentation match for these errors. I'd suggest you make a support ticket specifically for the error codes and:

specify you are not asking for custom code help
you already understand how to use the REST API endpoints
you only need clarity on the meaning of these errors when using the endpoint

Best,

Jaycee

Re: /automation/v4 API HTTP 400

shubjain — Fri, 13 Jun 2025 07:47:25 GMT

Hey, thanks for your response! I actually already spoke to Support and they suggested I post here so the developers could have a look - do you know anywhere else I may be able to ask?

Re: /automation/v4 API HTTP 400

Jaycee_Lewis — Tue, 01 Jul 2025 15:52:12 GMT

Hey, @shubjain I don't, unfortunately. My instinct is to press support for an answer on the error codes, specifically because those are generated via the product and not something a community member would have access to. Where our community members can help is with looking at code issues or troubleshooting your request. If you want to share the request and response here, maybe we can, as a community, take a look.

Talk soon! — Jaycee