Workflow API get all actions

Develop, Build & Integrate APIs & Integrations
1

Hello,

When I try to get actions from workflows from endpoint "

/automation/v3/workflows/:workflowId", I only get a single path within all branches of the workflow, the left one. All related filters and actions are good for this path btw. I dont know if its a strange functionnality but this happens on all worflow.
If you have any ideas on how to get all branche’s actions or a clear answer that it’s impossible to do could be very helpfull,
Thanks !

2

Hey, @JLegendre8 :waving_hand: Thanks for flagging this. I get the same result from a quick test. Here’s what I did:

  • Created a contact-based workflow

  • No enrollment options

  • Added two branches – `A` and `B`

  • Added a single action to each branch – send an email for A and clear a property for B

  • Made a request to the endpoint you listedGET https://api.hubapi.com/automation/v3/workflows/51502686​

  • Only got back `actionId 1` aka the “left branch”

    "name": "Testerrr-NOV23",
 "actions": [
 {
 "type": "BRANCH",
 "actionId": 1,
 "filters": [
 [
 {
 "property": "firstname",
 "value": "Bob",
 "type": "string",
 "filterFamily": "PropertyValue",
 "operator": "EQ",
 "withinTimeMode": "PAST"
 }
 ]
 ],
 "rejectActions": [],
 "acceptActions": [​

I reached out to the owner of these endpoints to see if this is “working as designed” or if there is an issue in how the response is returned.

Talk soon! — Jaycee

3

Thanks @Jaycee_Lewis, I hope this can be cleared up while I’m still working on it !
Talk soon !

4

Hi, @JLegendre8 :waving_hand: I found a resource internally and got our answer.

This is working as designed. The issue is due to the endpoint predating the release of branches in workflows. There isn’t a way to force the endpoint to return multiple branches or coerce that data from another of the existing endpoints for Workflows.

I don’t have a roadmap or date to share, but my suggestion is make sure you’re subscribed to the HubSpot Developer Changelog so you are the first to know when the revamped endpoints get released publicly.

Best,

Jaycee

5

I agree that this is a major limitation to the Workflow API. We currently use a workflow to sort our lead distribution and having an API that can check the current branch filters, I could then code comparison check to where we currently store our data and then update the filters accordingly. This would allow us to have this automatically update everything from one document, instead of having to change multiple sources manually.

6

This issue hasn’t been fully solved. There is still a massive, glaring gap in the API for workflows.
We get the branches, but cannot read or set the logic that us used in the branching e.g. is equal to, contains, starts with etc…

8

Hi @OJ_ONT and all,

Thanks for reaching out to the HubSpot Community!

I’m glad to share that this is now actually supported. Looking at the Create a workflow endpoint (workflows v4 API), LIST_BRANCH actions include a filterBranch with nested filters, each of type PROPERTY, ASSOCIATION, PAGE_VIEW, EVENT, etc. The operator/comparison logic (equals, contains, starts with, etc.) lives inside those filter objects, similar to how list filters work, each PROPERTY filter carries an operator field (e.g., EQ, CONTAINS_STRING, STARTS_WITH).

If you’re calling the GET/read endpoint and only seeing branch connections without these filter/operator details, that would point to a gap in what’s returned versus what’s accepted on create. If that’s the case, I’d suggest sharing this via the HubSpot Developer Feedback form here.

Can you share which specific endpoint (GET vs POST) and a snippet of the response you’re getting? That’ll help confirm the behavior.

I’d love to hear from our Top Experts: Hi @Mike_Eastwood, @zach_threadint and @evaldas do you have suggestions, please?

Thanks so much and have a wonderful day!

Bérangère

This post was created with the assistance of AI tools