Hi, we’re testing the Hubspot integration. One issue is that many fields are mapped as text string fields from Hubspot, even when they are defined as limited choice pick-list fields in Hubspot. The downside to this is that it impossible to build certain views in Fibery from the data, e.g. create a b…

Also I notice that the hubspotlink URLs saved to Fibery have the host app.hubspot.com, whereas our HS account uses app-eu1.hubspot.com (presumably because its stored in an EU data centre). This means that any link clicked from Fibery redirects to a Hubspot accounts view to select our account, but th…

Hi! Sorry for the late reply :disappointed_relieved: Unfortunately none of our integrations support single & multi-select fields That improvement is in our backlog though and noted your request :muscle: The second issue seems to be a bug to fix, so forwarded it to the developer!

Hi again! Glad to say, that the issue was fixed You can check that already, but full sync is required to update links in existing entities Many thanks for the report :slight_smile:

It seems like almost everything that gets synced other than text fields just gets set to read-only in Fibery…is this the intended behaviour? Even number and date fields, which seems super weird. If so, I guess the solution is to essentially clone the original synced hubspot entity as a completely …

What would you want to happen if you changed data synced into Fibery? Change it back in the source app (e.g. Hubspot)? If so you want Bi-directional integrations/sync . If not I am curious to know what would solve your need. :slight_smile: I think in general the point of syncing data 1-way (as is th…

I would want the synced entity’s fields to be usable and functional within Fibery, instead of just a static snapshot of what the fields were at the time of sync. Because most of the fields appear to be read only, I can’t really do anything with the synced entity and need to use an automation to rec…

Yep, already voted for it weeks ago. :slight_smile: I just don’t think that allowing fields on a synced entity to editable absolutely requires a bi-directional integration.

I think making them editable arguably requires a one-time sync (not just 1-way but 1-time). Either that or something like: An indicator when a field has been edited in Fibery and does not match the source data (and some way to make clear that this change is not reflected in the data source, i.e. t…

One reason why the Fibery syncs are almost all unidirectional is that bidirectional sync is hard, since it implies that there exists a mechanism for conflict resolution when data is independently changed in two places, and realtime sync is not possible. Assuming that users don’t want to leave Hubsp…

Fields synced from Hubspot

Get Help

Oshyan December 5, 2023, 5:31pm 8

It’s not a bug. Check out the other thread I pointed to and vote for it if you can because I think bi-directional sync is what you want (and e.g. Coda, Notion, and others already have this for more tools than Fibery does).

Topic		Replies	Views
January 5, 2023 / Select Fields to sync in existing integrations Changelog	4	555	January 19, 2023
[FIXED] Hubspot Integration Keeps Resetting Field Sync Settings Bugs & Issues	4	86	November 11, 2024
Bi-directional integrations/sync Integrations	63	4311	April 9, 2026
Hubspot Integration Get Help	5	476	March 22, 2022
January 26, 2023 / 🌕 Full add via Forms (experimental), Table of content (experimental), Hubspot v4 support Changelog	12	1202	January 14, 2024

Fields synced from Hubspot

Related topics