This is my first post in this community, and I hope it’s descriptive enough for everybody to understand.
I have created a workflow which posts a webhook to Zapier which in turn posts a Slack message in a channel containing the full name of the contact, company name, a company description, contact owner, and amount/value. This is all triggered when a deal is won, however, when a deal is won, this workflow is triggered for each contact associated to that deal which results in multiple posts in slack whilst I only want one post per deal.
Is there a way to work around this and either consolidate all contacts associated to the deal or maybe just post one primary contact?
Hey @DavidAndersen thanks for the detailed question. So to confirm: your goal is to send deal record to slack? Are you able to share a screenshot of the workflow you have built? @bradmin do you think this is possible?
Help other HubSpot searchers find this post quickly by accepting this solution today.
Q: Is there a way to work around this and either consolidate all contacts associated to the deal or maybe just post one primary contact??
Short A: Not with HubSpot built-in functionality.
Longer A:
In a loose integration scenario like the one you’ve built you need to specify a *primary* contact. Since HubSpot doesn’t differentiate between the priority of contacts associated with a deal, you’ll need to handle that yourself.
Maybe create a custom contact property -- e.g., Primary Contact (Radio select with a single option ‘Yes’). You’ll then need to use this property when identifying who the primary contact should be for each deal.
Once done, you can use this criteria to further refine your workflow enrollment trigger so as not to pick up the other (non-primary contacts) associated with each ‘closed won’ deal.
Make sense?
Finally, if you don’t want to modify your workflow enrollment criteria you can let Zapier ‘pick’ based on your new Primary Contact property.
This was actually one of my thought too. I guess I hoped that it would be possible to create workflows triggered on not only contacts but also company and deals. However, I think this will be the way we have to go.
I hear you David. The reason this ‘primary contact’ thinking is sorta 2nd nature for us now is because we’ve been seeing Account Based Marketing (ABM) clients have great success using a tool the bada$$es from OrgChartHub introduced called … wait for it … OrgChartHub. haha
One of the things we like most about OrgChartHub is that it allows us to graphically differentiate between ‘Influencers’ and ‘Blockers’ in a familiar org chart format. And, as a native HubSpot integration, it’s available right inside each contact and company record for all HubSpot users portal-wide. Sweet.
