I would love to be able to add in the new association labels using a workflow - rather than needing to do this manually.
this would enable businesses who have contact A who makes a booking and Contacts B, C, D etc who attend a course or an event flagged as attendees. so a business knows which are valuable contacts.
It would also be helpful to be able to use a workflow to send different communications to clients based on their association tag.
I know that everyone on this thread is eagerly awaiting a beta. We're actively working on this functionality and if you want more information of what will likely be included in our first release, I'd recommend checking out the "In Development" notification that went out last week. You can find this by navigating to Product Updates in your HubSpot portal and looking for "New Workflow Actions to Automate Association Processes."
We'll provide another update when we get ready to open up a broad beta.
I'm Maggie from HubSpot's product team. I'm excited to announce that we're actively working on the ability to manage association labels via workflow. We're hoping to have something in beta for you all to test out within the next few months.
I also want to share this Knowledge Base article which outlines the ways that you can already use association labels in workflows (for things like enrollment) as it seems like there are a few questions in that space.
Thank you for all of your thoughtful feedback and examples! It helps us make sure that we're building the right thing 😊.
Hi everyone, I don't have much in the ways of an update on this feature as we are still working through some major blockers. There is a limitation in how we find records to be associated, making it difficult to complete our set of features. We are still working hard on this problem and will have more updates along the way.
@04262 that feature is now live to all so it's no longer in the Beta page.
@RyGuy the changes we're working through are towards the next set of features I'm referencing, for example, the Set Association Label action. Therefore there wouldn't be much if anything changed to the existing beta functionality. Definitely feel free to message me with details if you'd like.
@jaybaum I just met with our Associations team and discussed that hard limit. No hard decisions were made but we would like to fix that as well and could see traction in the coming months. I would recommend opening an idea on our forum so we can track progress, otherwise we'll hopefully have good news down the line
As it so happens, today was going to be the day I gave an update as we've made some major breakthroughs recently that we wanted to share with everyone.
The new Data Panel beta feature is currently going through the final weeks of "beta testing" and will soon be available to all customers. We had a rather tricky setback this past month that took our entire team time to sort out but as of this week we've sorted out all the kinks and are back to working on the followup functionality needed for a "Set Association Label" action. While I can't give an estimate (for fear of hitting another setback and dissapointing people), I can say we have a much more clear line of sight to our goal and have many engineers actively working on the solution.
The good news is that this next milestone will include more than just the Association Label action. We are going to have the ability to support more field types and provide finer granularity on the types of records/data that can be pulled into a Workflow.
@RyGuy Thanks for pointing people in the right direction.
As for lack of functionality, I'm 100% with you, it leaves us wanting more as well. We're working on scaling issues at the moment to bring what we think is the full power of the feature: pull one (or more) values from any object, event, integrator object, without restrictions (within reason in terms of scale). If you have feedback or recommendations, please let us know.
Sorry about the public beta link not working anymore, everyone. It looks like we had an issue with the way those betas work that prevented us from exposing the new feature in this manner.
Here's a short update from the team. Now that the [Public Beta] Data Panel with associated record data in workflows is open to the public, we've begun working on the "Set Association Labels" action that everyone in this thread has been patiently waiting for. After we complete our exploratory phase for the project, the team will be able to give a rough estimate on when we'd expect to have this ready for our beta testers. Stay tuned for more information.
@jaybaum sorry, that type of work is not related to the Workflows tool so we're not able to work on that directly. However, I will pass along that piece of feedback to the relevant team and see what can be done about that.
@NPW Yes, we're planning on adding support for almost every field. The Internal Email Notification is currently being worked on and should be ready in a few weeks.
Sorry to dissapoint about the pace of the setting of association labels, we'll continue to work hard on that and give an update once it's ready.
As we work hard on the Data panel with associated data private beta, I wanted to give another update as there has been some confusion surrounding our current work. While we have not started on the work to automatically apply association labels using the Workflows tool, we are prepping for it. The beta I linked to in my last message refers to a feature that is NOT to apply association labels using our tool. Instead, it allows the use of associated data in fields across the app, much like the "personalization tokens" that can be inserted into many text fields. Read below for more information:
A quick update based off our last update from January. We had issues come up that delayed us by a few weeks but should now be back on track. To remind everyone, the beta we're working on is a preliminary feature that will allow users to use a lot more HubSpot/external data across many Workflow fields. This is going to be one of our larger project releases in a while and once the (hopefully short) beta period on that is done, we'll then be able to start on the beta for the Associations work everyone in this thread is interested in.
So to reiterate, the beta that's going to go live soon is not directly for Associations work, but is indirectly related and required for us to start that work.
Making promises on when it'll be ready can only end poorly so instead we can give an update on the work and what our current blockers are:
- The initial beta to allow users to use data from many different sources went through the first round of testing and while we found a few major bugs, we've since patched most of them. Once we do a second round of testing, we'll start the private beta (and will invite anyone in this thread to join)
- The work needed for what everyone in this thread is looking for, a way to automate association/association labels, requires the previous feature to go live. Once that's live and stable, the new data sources availability would make it possible for our teams to build out a feature that could use this data for the purposes of manipulating associations
Once the first bullet point is done (and only then) we'll be able to move on the Association work.
As always, we'll try to update this thread and any related threads as we make progress!
The team has been hard at work for the past few weeks as we finish up work on the beta for our Data access feature (needed for us to start work on the Associations action within Workflows). Know that we're monitoring this thread on a weekly basis (or even daily) so as soon as that beta is ready to open, I'll post a link for those that want to join. We've had positive feedback from our preliminary alpha testing so we expect the beta to go by quickly, meaning even if you don't join this beta you'll have access to the new Data feature shortly after.
Depending on the amount of feedback we get during this phase we'll start to form (finally) a timeline for the Association feature everyone in this thread has been asking for.
I wanted to give an end of year update as we've been getting lots of requests for this feature. As we stand, our original estimate is still on track. The related features we needed to finish before starting on this associations request are due to be completed mid January. Once that goes into Beta, we'll work in parallel to both incorporate public feedback, as well build out functionality related to associations within Workflows.
We'll likely post a link to the January Beta in this thread so unless we have delays, expect great news early 2023
Hi @emmaboyd we're still actively working on the tangential projects that will make this one possible. We don't have a good timeline but expect to have those other projects done by the end of the year, after which we would be entirely ready to tackle this project.
We (the team that builds the Workflows editor tool) have a need for this feature as well so we are building all the necessary "building block" foundational features we need to make the association action a reality. We will update this thread once we get a timeline as we still have discovery work to do before we can commit to building it. The exciting news is that the CRM's association capabilities are also growing, making this action even more valuable to build.
Posting this on behalf of a customer. This feature would be incredibly helpful especially when dealing with thousands of deal records that need a contact association label. The current workarounds are very manual and inefficient, requiring an export of all deals, splitting the deals into rows for each associated contact and then reimporting the excel with the associated label. A workflow would make all of this so much easier.
This would save customers a lot of time and effort, so please prioritise this :')
It would be great to have the option to set an association label using workflows especially in cases where multiple tickets are created based on the different stages of the associated deals. Mapping an association label automatically as and when a ticket is created for a deal will allow us to build more personalized workflows based on the association labels of the tickets. Adding them manually is a pain considering the sheer number of deals that come through.
100% agreed. I've got three labels for one custom object, and I would love to have the ability to set the labels in a workflow. Manual is a giant time suck.
This seems like an absolutely necessary feature - why can't we do this already? I'm currently setting up a Custom Object to track Referrals made by an existing customer or partner for a new prospect. It would be incredibly helpful to associate who is the Primary (prospect) and who is the Secondary (referrer) within a workflow.
We need this improvement as soon as possible because all our workflows depend on it. We can't be associating tags manually for every business we create.
I am agree with everything who was said above this would be super usefull !
Example from my case, because our product is sold by a distribution network, every distributor has its own deal. It could happen that few distributors send the same lead in the same period of time, so we need to identify wich deal is the main one and wich deal we have to automatically close because it was sent too late.
Before this feature arrives, i have no idea of how to deal with that...
+1 to what everyone else has said. We've wanted multiple companies associated to a deal and labels for a long time, come on Hubspot - add the automation feature!
Please add this ability! Not having it makes the whole process of using them completely manual, and almost useless when trying to use them with deals that are created via automation.
My goal: Lead submits form, deal is created on form submission, contact who submitted form gets 'associated label' of Customer.
Yes please - we need to be able to create deals from form submissions (via a workflow) and label the Contact-Deal association at the same time, as needed for automation downstream.
Hugely necessary, especially when creating a new object via workflow.
When a new financial contact is added to a custom object I need a way to mark them as such so that I can be sure that the right person gets the right comms.
Ideally we could create associations themselves between two existing records via a Workflow, but I imagine that might be asking for a little too much.
