Hey Guys, Really need this to be implemented asap. Otherwise, it makes my OS implementation not scalable.
At my client there are several teams like Activation, Customer Success, etc.
Each team has their own Pipeline with similar or different Pipeline Stages in HubSpot.
I’m building an OS pilot project focused on just one of the teams atm, however, it’s already tricky to get data that’s intended for one of the teams without using filters on the set of 20+ Workflow stages that I get for Ticket db through the standard Fibery-HubSpot integration.
Now, 20+ Workflow stages is indeed a crazy story and this is now part of HubSpot cleansing initiative I started. But, nevertheless, there can be custom stages used by specific teams other than a “standard set”, and I have currently no means to see which HubSpot Pipeline those Workflow stages belong to, so I could quickly filter on the Team db level rather than on the field level like now to ensure only the Team/Pipeline specific stages are shown:
In Hubspot, each value for the State field belongs to some ‘Pipeline’ and each Team can have its own Pipeline. And after syncing, you want the State field in Fibery to store the information about which Pipeline each State option belongs to.
Right?
I think there is very little chance that this will get implemented any time soon, but I can ask the devs to note it as a FR.
In the meantime, I think your easiest option is to just add a Pipeline field to the State select i.e. a relation (many-to-one) to a Pipeline db, and then link your Pipeline db to the Team db.
Then you can manually recreate the relations that exist in HS
Chris, thanks for prompt reply. I know I can add my Pipeline db. But they can also change the data in HubSpot and then I’m screwed with my mappings. I’d prefer the native integration to take care of that.
