Skip to content

An action a flow PUT adds, or re-adds, must have an `actionId` at or above the flow's current `nextAvailableActionId`; reusing an older or lower ID returns 400 "Invalid request to flow update". Renumber from `nextAvailableActionId` instead.

Measured

Checked

Checked October 21, 2026 on a HubSpot developer test account
Checked October 16, 2026 on a HubSpot developer test account

Area

Tags

workflows, update, put, action-id

More facts from this area

In the Automation v4 spec, an AB_TEST_BRANCH action routes each path through testBranches[].connection.Source pending
The workflow action-type catalog (GET /automation/2026-09-beta/action-types) carries each type's actionTypeId, name, group and input names only. It has no field that says an action is Breeze, uses AI, or consumes credits, so credit-using actions can only be recognized from a curated list of ids.Measured
The action-type catalog GET /automation/2026-09-beta/action-types doesn't list the classic actions 0-3 (task), 0-8 (internal email) or 0-11 (rotate owner), though flows using them save and run.Measured
Add to static list is workflow action 0-63809083 at version 5, with fields: { listId, targetObject: "{{ enrolled_object }}" }.Source pending
A multi-checkbox "add to existing values" edit (0-5) is value: { type: APPEND_OBJECT_PROPERTY, appendPropertyName }, and it works together with association. A guessed fields.appendValue is silently dropped.Measured

Spriggit uses these facts when it plans changes. See something out of date? Email [email protected]