# \[FIXED\] HubSpot-Fibery: Inconsistent Hubspot backlinking field naming across dbs

**URL:** <https://community.fibery.io/t/fixed-hubspot-fibery-inconsistent-hubspot-backlinking-field-naming-across-dbs/11108>\
**Category:** Bugs & Issues\
**Tags:** integration\
**Created:** [July 27, 2026, 9:34am UTC](https://community.fibery.io/t/fixed-hubspot-fibery-inconsistent-hubspot-backlinking-field-naming-across-dbs/11108 "2026-07-27T09:34:52Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![myg\_ge](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/myg_ge/32/12457_2.png) [@myg\_ge](https://community.fibery.io/u/myg_ge)\
**Post date:** [July 27, 2026, 9:34am UTC](https://community.fibery.io/t/fixed-hubspot-fibery-inconsistent-hubspot-backlinking-field-naming-across-dbs/11108/1 "2026-07-27T09:34:52Z")

</div>

Sometimes the HubSpot backlink field is called HubspotLink, sometimes it’s called Hubspot URL.

Is there a reason behind this having the same nature field named differently per different db (eg, in Call db this field is named Hubspot URL whereas in Contact db it’s called HubspotLink)?

---

<div class="post-metadata">

**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\
**Post date:** [September 17, 2026, 12:05pm UTC](https://community.fibery.io/t/fixed-hubspot-fibery-inconsistent-hubspot-backlinking-field-naming-across-dbs/11108/2 "2026-09-17T12:05:25Z")

</div>

Fixed in latest release

> [@September 17, 2026 / New Fibery AI Agent, Whiteboards and AI, Space templates with files and images, OAuth Applications](https://community.fibery.io/t/september-17-2026-new-fibery-ai-agent-whiteboards-and-ai-space-templates-with-files-and-images-oauth-applications/11298):
>
> New Fibery AI Agent The most frequent complaints we kept hearing about Fibery AI agent are that it’s quite unresponsive and feels veery slow sometimes, doesn’t know what it can do and cannot do, and acts proactively in cases when it shouldn’t have. All three are consequences of the agent architecture that we’ve chosen a year ago: router agent on top with area-specific agents to delegate to. Passing relevant context between sub-agents and making sure router really knows where to delegate the reuq…

---

<div class="post-metadata">

**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\
**Post date:** [September 29, 2026, 2:09pm UTC](https://community.fibery.io/t/fixed-hubspot-fibery-inconsistent-hubspot-backlinking-field-naming-across-dbs/11108/3 "2026-09-29T14:09:02Z")

</div>