# Hubspot Integration \[DONE\]

**URL:** <https://community.fibery.io/t/hubspot-integration-done/1292>\
**Category:** Integrations\
**Created:** [January 11, 2021, 6:03am UTC](https://community.fibery.io/t/hubspot-integration-done/1292 "2021-01-11T06:03:08Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![B\_Sp](https://avatars.discourse-cdn.com/v4/letter/b/e8c25b/32.png) [@B\_Sp](https://community.fibery.io/u/B_Sp)\
**Post date:** [January 11, 2021, 6:03am UTC](https://community.fibery.io/t/hubspot-integration-done/1292/1 "2021-01-11T06:03:08Z")

</div>

I wanted to suggest this one for a few reasons:

- Hubspot has a very similar in-app communication messenger to Intercom. So you could get the same Feature Feedback potential that is currently a cornerstone of the Product Team Workspace ([Fibery Product Workspace](https://community.fibery.io/t/fibery-product-workspace/1120)) with the integration of the Intercom conversations from customers, which are later synthesized into Fibery for Feature Prioritization.

- Hubspot has a nice CRM + Email function, so you’d be able to use those, hopefully integrating with some CRM capability in Fibery - and handle some of the ask in here around Emailing. And since Fibery itself is not using Fibery for Sales Reachout, this is a chance to integrate an outside tool that does that as I’ve never heard of [Snov.io](http://Snov.io) and I doubt it will be as widely-used by potential Fibery newcomers as Hubspot.

Thanks!

---

<div class="post-metadata">

**Author:** ![Polina\_Zenevich](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/polina_zenevich/32/480_2.png) [@Polina\_Zenevich](https://community.fibery.io/u/Polina_Zenevich)\
**Post date:** [January 15, 2021, 9:09pm UTC](https://community.fibery.io/t/hubspot-integration-done/1292/2 "2021-01-15T21:09:39Z")

</div>

Hi!  
Have that in the backlog, now are collecting requests to choose which CRM tool will be the first one - Hubspot, Pipedrive, etc.  
Noted your request 🙂

---

<div class="post-metadata">

**Author:** ![B\_Sp](https://avatars.discourse-cdn.com/v4/letter/b/e8c25b/32.png) [@B\_Sp](https://community.fibery.io/u/B_Sp)\
**Post date:** [March 8, 2021, 8:06pm UTC](https://community.fibery.io/t/hubspot-integration-done/1292/3 "2021-03-08T20:06:29Z")

</div>

Since I just read about Hubspot Integration being on the radar in the February Chronicles, wanted to flag this up again. @mdubakov mentioned also here:

> [@CHANGELOG: February 18 / Mention people in the inline comments, text highlights, bug fixes](https://community.fibery.io/t/changelog-february-18-mention-people-in-the-inline-comments-text-highlights-bug-fixes/1381/8):
>
> So after Zendesk we’ll add HubSpot integration in fact.

the potential of the Hubspot integration.

So I have a question: Since Hubspot has a similar functionality to Intercom with an on-site chat bot/support window, do you guys plan to set up a similar integration than with Intercom for Feature collection and tracking requests? For that matter, Zendesk also has very similar functionality. However, both Hubspot in particular, and Zendesk, have reasonably CRM’s which could be also integrated into Fibery. Intercom does not have any CRM.

I’m wondering as my team is trying to use Fibery as a bonafide CRM, but with some missing features still like [Email Integration](https://community.fibery.io/t/email-integration-for-crm-use/1222), we are considering starting out with Hubspot, and integrating its CRM with Fibery would be nice. If we could also set up the chatbot/messenger in Hubspot much like the way the basic Intercom service works, we’d get the benefit of an even better integrated CRM/support solution outside Fibery, that we could hopefully integrate with other work inside Fibery very easily. This is a superior solution than trying to use Intercom, and then another tool like Hubspot for CRM, where you often have one client writing to you in Intercom, who’s the same client you are tracking your CRM activity on.

Thanks for listening!

---

<div class="post-metadata">

**Author:** ![B\_Sp](https://avatars.discourse-cdn.com/v4/letter/b/e8c25b/32.png) [@B\_Sp](https://community.fibery.io/u/B_Sp)\
**Post date:** [April 28, 2021, 4:32am UTC](https://community.fibery.io/t/hubspot-integration-done/1292/4 "2021-04-28T04:32:53Z")

</div>

@Team Fibery, do you guys have any update here? It was on this twitter WIP:

> <https://twitter.com/fibery_io/status/1381578034076061697>

But no longer on the one you published today.

Thanks!

---

<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:** [April 28, 2021, 7:51am UTC](https://community.fibery.io/t/hubspot-integration-done/1292/5 "2021-04-28T07:51:40Z")

</div>

Developer who started this feature went for 3-weeks vacation, so it is on hold, but it will be resumed soon.

---

<div class="post-metadata">

**Author:** ![JMaynier](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/jmaynier/32/1727_2.png) [@JMaynier](https://community.fibery.io/u/JMaynier)\
**Post date:** [June 8, 2021, 11:32pm UTC](https://community.fibery.io/t/hubspot-integration-done/1292/6 "2021-06-08T23:32:59Z")

</div>

I’m also interested in Hubspot integration. We currently use SalesForce but considering switching to Hubspot (SF is a very expensive glorified database, badly executed, horrible UX and perf) since Fibery will not be ready to be a CRM before quiet some time (no native email features or deep integration with Gmail, no mobile app, no contact integration with Google contact, no reminder, etc)

---

<div class="post-metadata">

**Author:** ![B\_Sp](https://avatars.discourse-cdn.com/v4/letter/b/e8c25b/32.png) [@B\_Sp](https://community.fibery.io/u/B_Sp)\
**Post date:** [June 9, 2021, 2:14am UTC](https://community.fibery.io/t/hubspot-integration-done/1292/7 "2021-06-09T02:14:33Z")

</div>

Great post @JMaynier! This is a great description of what we need in Fibery for native CRM:

> [@JMaynier](#):
>
> (no native email features or deep integration with Gmail, no mobile app, no contact integration with Google contact, no reminder, etc)

and all of that stuff is actually available in a lot of competing apps, like Asana, Wrike ClickUp, etc. etc. but none of them can match Fibery’s relations and networked thought handling, as well as product dev capability drawing from client input. I really encouraged the @Team Fibery to prioritize these basic features so we don’t have to rely on an integration with Hubspot, which remains to be seen how deep it will be anyway. Ideally we could just do it all in Fibery if we just get those items you mentioned that would make Fibery itself a great CRM!

Thanks again for this post and description of the need!

---

<div class="post-metadata">

**Author:** ![helloitse](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/helloitse/32/498_2.png) [@helloitse](https://community.fibery.io/u/helloitse)\
**Post date:** [June 25, 2021, 2:35pm UTC](https://community.fibery.io/t/hubspot-integration-done/1292/8 "2021-06-25T14:35:33Z")

</div>

I’m looking forward to a basic integration with Google Contacts and Calendar and eventually Gmail.  
The google contacts integration may be a fun one to dev myself if the open up the apps platform to third party developers.

That said, is the ask to prioritize and Hubspot integration or native alternatives? I feel lost reading this thread lol

---

<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:** [July 30, 2021, 3:01pm UTC](https://community.fibery.io/t/hubspot-integration-done/1292/9 "2021-07-30T15:01:19Z")

</div>

HubSpot integration is released. Please check it and give us your feedback!

> [@CHANGELOG: July 30 / Documents and Rich-text History, HubSpot integration](https://community.fibery.io/t/changelog-july-30-documents-and-rich-text-history-hubspot-integration/1855):
>
> Documents and Rich-Text History Starting this week, rich-text Fields and Documents have version history: [doc-history] Here are a few scenarios when version history can help (or even save the day): Somebody (Alex, you again!) has accidentally erased a significant part of your doc and you need to restore it. There is an unexpected paragraph and you’d like to find out who has added it. You rewrote a specification during an all-nighter — now you’ve sobered woken up and realized it’s all been a…

---

<div class="post-metadata">

**Author:** ![Oshyan](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/oshyan/32/11431_2.png) [@Oshyan](https://community.fibery.io/u/Oshyan)\
**Post date:** [July 31, 2021, 3:32am UTC](https://community.fibery.io/t/hubspot-integration-done/1292/10 "2021-07-31T03:32:15Z")

</div>

Fair warning: I haven’t used Hubspot before today. But I am looking for a ticket management/CRM/etc. system, and it was on the list of options to test. So I dove in today, and after about an hour of messing around, setting up some integrations (email, form, live chat), and creating some tickets, meetings, and notes, I connected it up to Fibery to see how it worked.

In general it’s good to see a reasonably significant amount of content makes it over. Numerous fields and their values, etc. But there are few glaring omissions so far, which may be somehow issues with my setup, or may just be limitations of the current approach, but in the latter case should definitely be addressed IMO.

The first is that the contents of _tickets_ appears to not be imported. There is no content in the Description field of my Ticket entities. In contrast, Notes seem to have imported their full contents, including images (nice!).

That said, Notes also did not seem to be linked to Tickets, even though these note were made on some of these tickets. In fact there seem to be a lot of missing links between info in Fibery, for example between a Task and the Ticket it was created from/for. Between an Email and the Ticket it became. Etc.

Also problematic, and something that does exist in the Discourse integration and is useful, is a link to these entities/locations in Hubspot, for each one of these. I don’t know if those kinds of “deep links” are available in Hubspot, but at the least you should be able to provide the URL for the ticket each Entity is associated with.

I’ll post again if I see anything else significant. But I think in general just trying to interlink things more would help a lot, if possible. So far it’s promising!

---

<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:** [July 31, 2021, 10:32am UTC](https://community.fibery.io/t/hubspot-integration-done/1292/11 "2021-07-31T10:32:49Z")

</div>

We’ll fix all these things @Oshyan, Thanks!

---

<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:** [October 4, 2024, 6:48am UTC](https://community.fibery.io/t/hubspot-integration-done/1292/12 "2024-10-04T06:48:46Z")

</div>


