Workflows v4 API: dataSources accepted on POST/PUT but not persisted

EdoardoP — Mon, 09 Mar 2026 18:23:36 GMT

Workflows v4 API: dataSources accepted on POST/PUT but not persisted

Summary

The POST /automation/v4/flows endpoint accepts and validates the dataSources field but does not persist it. A subsequent GET returns an empty array regardless of what was sent.

Test 1: POST with valid dataSources

Request:

POST /automation/v4/flows

{
  "type": "CONTACT_FLOW",
  "objectTypeId": "0-1",
  "canEnrollFromSalesforce": false,
  "isEnabled": false,
  "flowType": "WORKFLOW",
  "actions": [],
  "timeWindows": [],
  "blockedDates": [],
  "customProperties": {},
  "suppressionListIds": [],
  "dataSources": [
    {
      "name": "test_form_source",
      "objectTypeId": "0-15",
      "associationTypeId": 77,
      "associationCategory": "HUBSPOT_DEFINED",
      "sortBy": {
        "property": "hs_createdate",
        "missing": null,
        "order": "DESC"
      },
      "type": "ASSOCIATION"
    }
  ],
  "name": "Test workflow with dataSources"
}

Response: 201 Created (flow ID returned)

GET on the created flow:

{
  "dataSources": []
}

The data source was accepted but not persisted.

Test 2: POST with dataSources missing required "name" field

Request:

{
  "dataSources": [
    {
      "objectTypeId": "0-15",
      "associationTypeId": 77,
      "associationCategory": "HUBSPOT_DEFINED",
      "sortBy": {
        "property": "hs_createdate",
        "missing": null,
        "order": "DESC"
      },
      "type": "ASSOCIATION"
    }
  ]
}

Response:

HTTP 400 VALIDATION_ERROR
"Invalid input JSON on line 1, column 400.
Some required fields were not set: [name]"

This proves the API parses and validates the dataSources structure — it is not silently ignored during deserialization.

Test 3: POST with empty dataSources (baseline)

Request:

{
  "dataSources": []
}

Response: 201 Created, GET returns "dataSources": []

Test 4: PUT (update) also drops dataSources

Updating an existing workflow that has UI-configured data sources with new data source names via PUT /automation/v4/flows/{flowId}: the PUT succeeds, but GET returns the original data source names unchanged. The dataSources field is also not persisted on PUT.

Reproduction steps

POST /automation/v4/flows with a valid dataSources array containing an ASSOCIATION type entry with all required fields (name, objectTypeId, associationTypeId, associationCategory, type)
Note the returned flow ID
GET /automation/v4/flows/{flowId}
Observe dataSources is [] despite the POST payload containing valid entries

Expected behavior

Per the API reference, dataSources is a required field on POST /automation/v4/flows. The documentation specifies the ASSOCIATION subtype with required fields name, objectTypeId, associationTypeId, associationCategory, and type.

The API should persist data sources sent in POST/PUT payloads, or the documentation should clarify that data sources can only be configured via the HubSpot UI.

Actual behavior

The API deserializes the dataSources field (proven by validation error when name is missing)
The API accepts valid dataSources without error
The API does not persist them — GET always returns the pre-existing data sources (or [] for new workflows)
Data sources can only be created/modified through the HubSpot UI

Impact

Workflows that use {{ fetched_objects.<name>.<property> }} template references in action fields cannot be fully deployed via the API. The data sources must be manually configured in the UI after API-based workflow creation, and the HubSpot-generated data source names must then be copied back into the deployment tooling.

Environment

API version: Workflows v4
Endpoint: POST /automation/v4/flows, PUT /automation/v4/flows/{flowId}
Portal type: Enterprise

Has anyone found a workaround for this, or am I missing something obvious? Any insight would be appreciated.

This issue has also been submitted via the HubSpot Developer Feedback form.

Re: Workflows v4 API: dataSources accepted on POST/PUT but not persisted

BérangèreL — Tue, 10 Mar 2026 11:42:15 GMT

Hey @EdoardoP and thanks for reaching out to the HubSpot Community!

It's great that you've submitted the feedback form, thank you! This seems like a bug so I'd also reach out to our Support Team for this, including:

- The x-HubSpot-Correlation-ID from your API responses
- Your HubSpot Account ID
- The specific flow IDs from your tests
- The link to this Community post

Since the Workflows v4 API is currently in beta, it’s expected that some features may still be in progress. We appreciate your understanding as the functionality continues to improve!

Let's consult our Top Experts here: Hi @SteveHTM, @Christensen and @Anton do you have any insights to share with @EdoardoP, please?

Thanks so much and have a great day!
Bérangère

Re: Workflows v4 API: dataSources accepted on POST/PUT but not persisted

NSavi — Tue, 10 Mar 2026 18:31:40 GMT

You’re not missing anything. Right now the Workflows v4 API accepts dataSources but does not persist them.

It gets validated during the request, but the backend ignores it when saving the workflow. That’s why the GET response returns [] or the original values.

At the moment, data sources can only be configured through the HubSpot UI. The usual workaround is to create the workflow via API, then add the data sources in the UI and reference the generated names in your templates.

topic Workflows v4 API: dataSources accepted on POST/PUT but not persisted in APIs & Integrations

Workflows v4 API: dataSources accepted on POST/PUT but not persisted