Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Docs: Flows v4 API — same actionTypeId / type / enum-operator gotchas as nodejs SDK

Open
#498 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
58/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Quiet
Tech stack
python
Domain
api, documentation

Research direction

Start with the Python SDK's handling and documentation for POST /automation/v4/flows, then compare it with the linked reproductions and the four listed gotchas. Done means the SDK documentation or error messages clearly cover actionTypeId values, the required matching type, ENUM operator syntax, and non-nested event filter branches.

Written by the indexing model from the issue text.

Description

Cross-post of https://github.com/HubSpot/hubspot-api-nodejs/issues/695 — the same four Flows v4 errors surface when scripting workflows from this Python SDK, and the error messages mislead in the same way. Reproducible payloads and fixes: https://www.elemra.com/learn/hubspot-flows-v4-api-errors

Summary of what to know before hitting POST /automation/v4/flows:

  • Legacy actionTypeId: "0-13" returns HTTP 500. Use "0-63809083" (add) / "0-63863438" (remove).
  • Top-level type field is required and must match objectTypeId (CONTACT_FLOW for 0-1, PLATFORM_FLOW for 0-3).
  • ENUM properties reject IS_NOT_EQUAL_TO; use IS_NONE_OF with a single-element values array.
  • Unified-events filter branches cannot nest — promote to top-level eventFilterBranches[] entries.

Same offer as on the nodejs issue: happy to open a PR against the SDK's error messages or docs if useful.

Dominant language
Python
Stars
434
Forks
126
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from HubSpot/hubspot-api-python

All issues in HubSpot/hubspot-api-python

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.