APIs & Integrations

NKlein
Member

Getting error: Currently do not support SingleObjectCoordinates, but support is coming soon

We are attempting to use the workflow v4 api - we've launched an integration used by several customers.
Unfortunately, a recent customer was trying to use the application - and on the fetch_workflow API we started getting this error message and a 400.
Currently do not support SingleObjectCoordinates, but support is coming soon

Is there something the customer do to add support for this api?

0 Upvotes
2 Replies 2
Jaycee_Lewis
Community Manager
Community Manager

Getting error: Currently do not support SingleObjectCoordinates, but support is coming soon

Hey, @NKlein 👋 I'll think we'll need more information. Can you provide screenshots or any other details to help give more context. Also, which specific Workflow endpoint are you using? Lastly, are you able to reproduce this on your end? Thanks! — Jaycee


HubSpot’s AI-powered customer agent resolves up to 50% of customer queries instantly, with some customers reaching up to 90% resolution rates.
Learn More.


Did you know that the Community is available in other languages?
Join regional conversations by changing your language settings !
0 Upvotes
NKlein
Member

Getting error: Currently do not support SingleObjectCoordinates, but support is coming soon

Hi @Jaycee_Lewis thanks for the response.
It's a response to the endpoint `Fetch a specific workflow by ID`
https://developers.hubspot.com/docs/guides/api/automation/workflows-v4

We are able to reproduce this API call and are consistently getting this error on this workflow and a duplicate of that workflow. 

On newer or other workflows things are working well.

We've not yet been able to reproduce the conditions that lead to that error from a fresh workflow though.

I don't have access to the workflow to provide a screenshot via the UI.

Not sure if important , but the workflow is available from the v3 API (although under a different ID using the `workflow_id` and not the `flow_id`) - unfortunately we require being able to update it which is why we are using the v4 API.

0 Upvotes