We’re developing an integration with HubSpot that relies on the Workflows v4 API, particularly for retrieving/updating workflow details (see this reference). We’ve noticed that some workflows cannot be managed via the v4 API and return the following error message:
{"status":"error","message":"Currently do not support SingleObjectCoordinates, but support is coming soon.","correlationId":"e063bad6-e05d-2699-fb57-fe47b29a88dd"}
Over time, certain workflows that were previously accessible have become unsupported, but we haven’t been able to pinpoint why. Does anyone know what triggers this error and how to avoid it?
Below is an example response from the v3 API for one of the workflows that fails when viewed or updated via v4.
The error message is pointing you in the right direction, but not with a lot of clarity.
The message basically means elements or structures that aren't yet fully supported by the v4 API, often due to how they were originally created or migrated. Remeber v4 is still in beta and can change at anytime.
In the workflow you shared, the issue likely stems from the UNSUPPORTED_ACTION types in the actions array, combined with the migrationStatus flags. These tell us the automation platform has taken over managing the internal structure of the workflow, which is when this error tends to show up.
The v4 API does support DELAY_UNTIL_DATE, as long as it's used in a format the v4 API recognizes. These are usually assigned actionIds in the 0–35 range and use the newer JSON schema.
So what’s likely happening here is:
The workflow may have originally been created using an older UI or legacy logic.
As HubSpot evolves its automation platform, some workflows are being re-migrated or claimed by the backend.
This triggers the "SingleObjectCoordinates" limitation in the API, even if the actions themselves would be supported in a fresh workflow.
If you're programmatically creating workflows, stick to supported actions and make sure you’re formatting them according to the v4 docs.
If you're trying to update existing workflows, check for UNSUPPORTED_ACTION types using the v3 API first, so you can avoid targeting those workflows with the v4 API.
You might want to clone the failing workflow in the HubSpot UI, rebuild the structure cleanly, and try again — that can sometimes force it into a fully supported state.
I you want to know specifically about the SingleObjectCoordinates part, you're seeing that because your workflow includes an action block to "Set marketing contact status". If you remove that action block, you won't see the error.
The error message is pointing you in the right direction, but not with a lot of clarity.
The message basically means elements or structures that aren't yet fully supported by the v4 API, often due to how they were originally created or migrated. Remeber v4 is still in beta and can change at anytime.
In the workflow you shared, the issue likely stems from the UNSUPPORTED_ACTION types in the actions array, combined with the migrationStatus flags. These tell us the automation platform has taken over managing the internal structure of the workflow, which is when this error tends to show up.
The v4 API does support DELAY_UNTIL_DATE, as long as it's used in a format the v4 API recognizes. These are usually assigned actionIds in the 0–35 range and use the newer JSON schema.
So what’s likely happening here is:
The workflow may have originally been created using an older UI or legacy logic.
As HubSpot evolves its automation platform, some workflows are being re-migrated or claimed by the backend.
This triggers the "SingleObjectCoordinates" limitation in the API, even if the actions themselves would be supported in a fresh workflow.
If you're programmatically creating workflows, stick to supported actions and make sure you’re formatting them according to the v4 docs.
If you're trying to update existing workflows, check for UNSUPPORTED_ACTION types using the v3 API first, so you can avoid targeting those workflows with the v4 API.
You might want to clone the failing workflow in the HubSpot UI, rebuild the structure cleanly, and try again — that can sometimes force it into a fully supported state.
