I have a custom object ("Site") to which I will associate contacts.
The custome object is also associated with a "Company" object (The Site is a Company Branch, basically).
I'm thinking of making a workflow to ensure that contacts associated with the "Custom Object" (people who work on the site) become associated with the "Company".
However, I can't event set up a trigger for a Site-based workflow to identify associated contacts.
Could anyone point me to some examples of using workflows and associations?
Unfortunately, out of the box it's not possible to make associations using workflows. You have two options if you'd like to only do that within Hubspot :
You have operations profesionnal and can write a custom code
You can use a marketplace app called associ8 (check their docs, they do have working examples) that will add new actions in your workflows like associating a record with another from a separate object (custom or not)
In both cases, you would indeed make your workflow a site-based workflow, and in the workflow triggers select : contacts > create date is known. This way any contact that is associated with the site will trigger it. Here is an example with a test custom object on my portal (you'd replace bateau by site in your case) :
Then you would use one of the two ways aforementionned to make your association with the company.
Hope this helps ! If it does, please consider marking this as a solution 🙂
Best,
Ludwig
CTO @ Mi4 Hubspot Platinum Partner and Integration Expert
Passionate human, very curious about everything data and automation.
While there is no way to associate in workflows using standard HubSpot features, I believe you can custom code a solution for this in Operations Hub if that is something that might work for you. Here,here, and here are some recent forum threads on that for some context.
Also wanted to mention that Insycle (full disclosure, I work for Insycle as a product marketer) allows you to associate in Workflows, including custom object associations. You can use any field in your database to match the associations, and can even handle advanced use cases such as associations with multiple labels or child-parent associations, directly in the Workflow.
Unfortunately, out of the box it's not possible to make associations using workflows. You have two options if you'd like to only do that within Hubspot :
You have operations profesionnal and can write a custom code
You can use a marketplace app called associ8 (check their docs, they do have working examples) that will add new actions in your workflows like associating a record with another from a separate object (custom or not)
In both cases, you would indeed make your workflow a site-based workflow, and in the workflow triggers select : contacts > create date is known. This way any contact that is associated with the site will trigger it. Here is an example with a test custom object on my portal (you'd replace bateau by site in your case) :
Then you would use one of the two ways aforementionned to make your association with the company.
Hope this helps ! If it does, please consider marking this as a solution 🙂
Best,
Ludwig
CTO @ Mi4 Hubspot Platinum Partner and Integration Expert
Passionate human, very curious about everything data and automation.
I'm the Product Specialist for Associ8 and @LMeert is spot on (thanks for the shout out)! Associ8 can help automate this process.
In order for Associ8 to work, there needs to be a common property between the two objects you are trying to associate. For example if you are trying to associate a Contact to a Custom Object, then you can create a property on the custom object such as "Partner Domain" and use the Contact Token "Email Domain" to make the association.
Here is an example of an Associ8 Workflow:
I'd love to learn more about your use case so I can help you create an Asssoci8 workflow. Feel free to shoot me a message and we can setup a call!
Hey @NivaDonga, if you are referring to ASsoci8 - you can use Associ8 in both Standard and Custom Object based workflows!
The Associ8 action looks slightlydifferent in Custom Object-based workflows but the action works identically to how it works in Standard Object workflows.
LMK if you have more Qs or need to hop on a call to discuss your use case in more detail.