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.
@MaggieBExcited that this is now in Beta! I tested adding associations between the contact object and a custom object called members. I set the association to match based on email, but it fails to match when the additional email of the contact record matches the member object's email. We have a unique identifier for members that is a number since many share an email address. I set it up so we can associate multiple members with one contact record. This Beta works fine to remove associations between contacts and members. The previous "create record" workflow function works fine to create a contact if the email from the custom object member record doesn't match any existing contacts. The problem is that when the member record matches an additional email it will not create a new contact record because it shares an email with an existing contact record, and the workflow association with this Beta will fail because it can't match the emails.
Would be cool to copy association label at record creation. My use case : when the sales team close won a "group" deal with several companies associated, the HQ is set as primary. I create a Renewal deal with a workflow when the deal is won but currently, we loose the association labels, I would like to copy the association labels from the deal that triggered the workflow on that newly created deal
@MaggieB - thanks for your work on this. How do we copy an association label from one deal to another? Here is the use case I am trying to accomplish - the sales team are associating a Contact as the 'Implementation Lead' (as a Contact to Deal association). When the deal is Closed Won and an Implementation deal is created, we would like that assoication to be copied over to the new deal. How would I best accomplish this?
@MaggieB I've noticed a slight bug. I've been using the "Create associations" action in a workflow that is supposed to associate the enrolled contact to a company based on a matching field. There have been some successful associations (yay!), but the workflow "Action Logs" screen also shows "Action succeeded" even when the association was not completed. Any way this can change to show NOT successful if an association was not completed?
Example: the field I'm matching on should contain a number. This contact entered text, but the action log still showed the association as successful even though the fields do not match.
Thanks for working on this functionality. As a non-profit we use 'Deals' for our donations (incomings) and 'Tickets' to manage our Project Partnerships. To track how many donations we have supporting each project, we associate a large number of deals to a small number of tickets. To be able to automate these associations and labels through workflows is going to be a real game changer for us 🙂
In the workflow is it possible to specify which ticket you want it to associate with rather than 'matching property values'? E.g. If {custom field = X } associate it with the 'Whale Project' Ticket. If {custom field = Y } associate it with the 'Kelp Restoration Project' Ticket.
Automating the process of updating or removal of the Primary association label through workflows is not possible.
Example: The contact is associated with 'Microsoft Bing' with a Primary Label. And, if we want to associate all Microsoft.com contacts to 'Microsoft' company using workflows it's not possible.
My goal is to associate the Microsoft.com contacts with the Microsoft account and not with any other child accounts.
It sounds like you want to create a new record, associate it to the enrolled record and then label that new association.
Not sure if this has been addressed yet but I just set this up in our instance using a contact property. Our use case is that a contact will submit a form to nominate their doctor to be added to our network. We have a workflow that creates the doctor as a contact and associates it to the enrolled contact (contact who submitted the form). As part of that doctor contact creation step I set a custom contact property called Contact Association Label Trigger to Provider. Then, I use the new Apply Association Labels step to apply a Provider label to any associated contact that has a Contact Association Label Trigger value of Provider.
Create doctor contact and set custom property value
Apply Provider association label when custom property value matches
@MaggieB Thank you for the beta test and for adding workflow functionality for association labels! One feature that we are looking for is the ability to copy association labels from one custom object to another when creating a new record. This doesn't appear to be possible in the beta test. We would like the workflow to look at the association + association label on the original enrollment record and copy it over to a new record via the create record function. For some background, we use a custom object to track client projects and a workflow to clone those projects upon renewal. The workflow creates a new record, copies over the fields that stay constant (leaves others blank), and copies over the associations as well. These custom objects are often associated with more than one company because the project scope can include both a parent and annex company (or several companies), but not always. Using a custom object-to-company association label, we can identify which company should be listed as the primary on a project and which should be listed as an annex. Is copying the original association+label to a new record possible via the beta test? If not, is it something you can consider for future roll-outs? Thanks!
@MaggieB So excited this is in Beta!! Been waiting for this to simplify a lot of data management we have. One feedback item i would like to provide is being able to match on more than one field matching pair.
Use Case - I want to match open assignments to possible contacts based on 2 different fields that exist on both Deals and Contacts, Area of Work + State.
In the future it would also be nice to add even more fields to match because we have properties like skills and hours and pay range that would be nice to use as matching criteria. Would also be nice to be able to set the matching criteria similar to List Filters where you could have groups of criteria like Area of Work + State + Hours OR Area of Work + State + Pay Range.
@MaggieB and @zeke Would a good solution for use cases where they want to create a deal record from a contact-based workflow and apply an association label be to make sure a certain property is updated to something unique when the deal record is created, add a delay, and then add the Beta option to Create or Apply Association label?
An option in the Create record action to select the association label would be ideal, but while it's under review, would that be the best alternative solution? I have a customer wanting that very feature who called into support! Was so happy to share this with him.
Hi @MaggieB, would it be possible to join this beta? I've got a workflow creating an associated deal, and it would be amazing to add an association label to that newly created deal.
@ADerbyshire Apparently they have closed the beta for now, even as a paying customer with all Enterprise hubs I was given this response from support when I asked to be added.
"I was able to hear back from the more urgent request that you had for the workflow actions beta - the team has alerted me that at this time, we're pausing beta access while we focus on making improvements to ensure our systems scale effectively. We will resume adding customers within the next few weeks. Since you have requested the beta access through your product updates tool, you will be on the list when they start to open this process again."
@MaggieB I'm excited about the open beta right now & appreciate all the work your team is putting into this!
I have a roadmap question for this functionality - are you all planning to allow workflow enrollment based on association labels, in addition to workflow actions to add/remove/update them? I have several use cases where I could greatly benefit from setting up a "from scratch" workflow with filter-based enrollment, where I target contacts (or companies, deals, or tickets) that have certain association labels applied.
If not planned, is this something that you would consider? Or do you have suggested workarounds? I would even be open to creating active lists based on association labels (to use for workflow enrollment), but that doesn't seem to be a filter option for lists either.
Thank you for all of the feature requests. We're reviewing them and will be determining what we can support later this year. I'm seeing trends in the following requests: triggering workflows based on the application of an association label, applying an association label as part of the create & associate flow and copying associations from one record to another. Please keep the feedback coming-it's helpful for us to ensure we're prioritizing the right thing.
We have currently paused on adding new customers to the beta. There has been a ton of enthusiasm for these features and we're making updates to our systems to ensure that everything will continue to scale as efficiently as possible. We will resume adding additional customers within the next few weeks. No further action needed if you've already submitted a request.
I've noticed some bugs in the workflow steps to create new associations or to create/update/delete association labels.
The use case: We organize events and customers can bring event guests, when they bring a guest we also ask their email to send them the information of the event as well. In a workflow we either create a new contact or associate an existing contact. Creating the new contact is no probem, associating an existing contact based on a property (email in our case) gives a lot of mistakes
The matching propery values seems to be case sensitive, it does not match when one email has a capital letter somewhere, en the matching email does not.
Like mentioned a couple of comments before; even though the associated was failed to be made, the workflow still says "Action succeeded". If it fails it gives me this message in the details:
{"outputFields":{"hs_execution_state":"SUCCESS","message":"No associated object was found"}}
But the really weird thing is that even if the action succeeds, it usually gives me the message above as "action succeeded" but before that message the workflow first says "This action was initiated".
Could your team please have a look at the messages of succeeded and failed, ... Because it makes it really difficult to see where things go wrong and to built in safety systems in a workflow.
Will the workflow allow same object association when creating a record. Example: a Ticket based workflow creates a new ticket that is associated with the ticket that was enrolled. I can only see the option of associating to other objects (not same object association)
