Workflows API (v4 / 2026-09-beta) hides every flow that contains an "Edit record" action from an OAu

Hi HubSpot team,

I’m building a read-only public app (new developer platform, project-based, platform version 2026.09, OAuth, distribution: marketplace, required scopes: oauth, automation). App ID: 55373632.

What I see in two developer test accounts:

  1. Enterprise test account 149464563
  • GET /automation/v4/flows returns 200 with only the flows that have NO property-editing actions (a flow with just a Delay is listed).
  • Flows that contain an “Edit record” (set property) action are missing from the list. The 4 default ticket workflows are missing too.
  • GET /automation/v4/flows/5027280062 returns 403: “Access denied. Flow must be accessible via external APIs and contain no sensitive properties unless appropriate sensitive data scopes are provided.” (correlationId 01a0f995-81cf-73d1-b08a-d92439486093)
  • POST /automation/v4/flows/batch/read for the same ID returns 207 with FLOW_NOT_FOUND_BY_FLOW_ID.
  • Same result on /automation/v4/2026-09-beta/flows and /automation/v4/2027-03-beta/flows. GET /automation/v3/workflows returns an empty list.
  1. Professional test account 149464751 (all hubs set to Professional)
  • A new manually triggered contact workflow is listed while it is empty.
  • As soon as I add one “Edit record → Job Title = A” action and turn it on (flow 5027281135), it disappears from GET /automation/v4/flows (results: ).

The properties used are standard, non-sensitive contact properties (Lifecycle stage, Lead status, Job title, Industry, City). Adding crm.objects.contacts.sensitive.read is rejected at deploy (“scope isn’t available to this app”).

Questions:

  1. What exactly makes a flow “accessible via external APIs”? Is there an account or workflow setting?
  2. Are flows with “Edit record” actions created in the current workflow editor intentionally excluded from the Workflows API for OAuth apps?
  3. If a sensitive-data scope is required even for non-sensitive properties, how can a marketplace app request access?

My app only needs read access to list which properties each workflow sets. Thank you!

Hi @Altair and welcome, it’s so great to have you on the HubSpot Community!

Great questions, thanks for asking!

To start with, I’d like to share these resources for more information:

Given your app only needs read access to list which properties a workflow sets, and the gate seems to be triggering even on non-sensitive-looking fields, this looks like something to raise with our Support team (since you are on a paid subscription) to check if the sensitive scope can allowlist and to flag that non-sensitive standard properties appear to be invoking the sensitive-data gate.

I’d suggest including the link of this Community topic and both test account IDs when you reach out to our Support Team.

In the meantime, let’s see what our Top Experts have to say: Hi @Anton, @evaldas and @BarryGrennan do you have suggestions or workaround, please?

Have a wonderful weekend and thanks so much!

Bérangère

The crux of the issue, it seems, is that the new API endpoint doesn’t support many of the actions yet and if it doesn’t support it, you’ll get this error. Edit Record being one of the unsupported actions.

Even adding Edit Record to a workflow and then removing it will give you this error when it would previously pull fine.

Hopefully they’ll resolve this soon/update the endpoint.

Your repro makes this look less like a scope issue and more like the API deciding the whole flow isn’t externally readable once that action is present

One thing I’d be careful with meanwhile: don’t treat GET /flows as a complete workflow inventory. If a flow can disappear based on one action, not returned and doesn’t exist are two different states.

For an audit tool I’d flag the inventory as incomplte when this happens and keep the known flow IDs/raw responses, rather than silently reporting a clean subset

The Delay-only vs Edit-record comparison is probably the strongest repro to give Hubspot