I have a follow-up question related to an earlier discussion about syncing data from an external GraphQL API into HubSpot.
Since workflow webhooks and custom actions have limitations (no custom headers, execution time limits, etc.), I’m exploring alternative options inside HubSpot.
My question is: Can HubDB be used in any way for this use case?
Specifically:
* Can HubDB act as a table where external data can be stored or updated programmatically?
* Is HubDB intended only for CMS/website content, or can it be safely used for operational data?
* Can workflows or automation be triggered based on HubDB changes?
* Is HubDB suitable for any part of a sync pipeline, or should it be avoided altogether for this scenario?
I want to confirm whether HubDB has any role here, or if the recommended approach is entirely external orchestration using the CRM v3 APIs.
@Bhagwat - I think the answer to this is yes, but with some caveats. I routinely use HubDB for staging data imports (while I check consistency and validity for example) and then use APIs to move the data into HubSpot records. And HubDB is especially useful if you want to add date through an unvalidated call - the APIs are set up to enable this if required.
But, I think you might want to consider performance constraints - I have bumped into some limits when processing larger tables - and consider that HubDB data is (very perversely) is writeable with a standard core license, but only readable if you have at least a pro content hub subscription. And I don’t know of any way to trigger workflows based on data changes at present.
Hi @Bhagwat , HubDB can help as a staging layer, but it’s not a great fit for a true sync pipeline. You can write to it programmatically through the HubDB API and treat it like a lightweight table, but it was designed for CMS use cases and inherits those constraints.
There’s no native way to trigger workflows from row changes, and large tables tend to hit performance ceilings quickly (Accounts Dashboard | HubSpot )
For operational data, HubDB also becomes awkward because reading requires a Content Hub Pro subscription, so any internal tooling or integrations that expect consistent access end up tied to CMS permissions.
In most cases, you still end up orchestrating everything outside HubSpot and pushing final values into CRM objects or custom objects through the v3 APIs, which gives you proper automation triggers, associations, search, and reporting. If your external API is changing frequently or you need multiple systems to stay aligned, Stacksync handles the two-way sync layer so you don’t have to maintain custom middleware just to keep those CRM records current.