There are so many different CRMs out there that Dux-Soup customers use to help with their LinkedIn automation activities. Each of these CRMs has a unique user interface and different processes around customer relationship management.
Updating an existing record in your CRM* might seem tricky and impossible, so we decided not only to do a webinar on the topic, but also to follow it up with a blog. This way, if you can’t spare 30 minutes to take a look back at the recording - you can simply take 10 minutes, to give this blog a quick read instead!
We will talk about Dux-Soup’s new Message event on LinkedIn and ways you can transfer this message to your CRM.
*An initial profile record has to be completed also by Dux-Soup.
In order to add a contact to a campaign or create a new profile record in your CRM, the process is pretty straightforward. You have to create a new Zap and trigger a new profile Visit Event.
Note that automated visits result in two events: 1) for the initial profile view (create event); 2) after the robot opens the contact tab - this will include the email address if the prospect is your 1st-degree connection or you can use Dux-Soup points (update event).
To make sure your Zap won’t create any duplicates, ensure your workflow logic is as follows:
Trigger Dux-Soup visit event and find the contact in your CRM. If it doesn’t exist, create a new contact record.
This will ensure that your Zap doesn’t create any duplicate records in your CRM.
As an example, let’s create a profile record in Salesforce once Dux-Soup auto-visits profiles on LinkedIn.
Note, once you add Dux-Soup as your trigger app and ‘New Profile Visit’ as a trigger event, select your account and filter, Zapier will provide you with trigger sample data. Please take a notice of the field called ‘profileid’:
Every LinkedIn event that Dux-Soup captures contains different data, however ‘profileid’ on (or Profile ID depending on your version) is always available and therefore can be used as the unique identifier in your data - i.e. it makes the perfect data field with which to carry out ‘lookups’.
In order to make use of this field, it is recommended that you create unique field names (also known as custom fields) in your CRM first. For example, you can add a LinkedIn ID as your lookup value and LinkedIn URL if it doesn’t have this field yet. Click here to learn how you can add custom fields in Salesforce. Each CRM will have its own possibilities regarding creating custom fields - make use of them to ensure you get the data you want.
Getting back to your Zap: you will now need to add Salesforce as an action app, connect your account and choose an action event ‘Find or Create Record’. As mentioned previously, make sure you use LinkedIn ID from 'Profile ID’ as your ‘Search Value’:
Also, turn on the ‘Create Record if it doesn’t exist’ option:
After these steps, add the data that you wish Dux-Soup to collect and transfer to your CRM. It’s as simple as that! Dux-Soup has created an initial profile record.
Now, imagine you have received a new message from the same profile and you want to add this message to the same record.
Before we proceed with the Zapier setup, it’s important you know that Dux-Soup’s Message events are captured when the Message Bridge checks your LinkedIn inboxes. This feature is located in the Options, Connect tab:
So to make use of this feature, make sure it’s enabled!
To add a message to the profile in your CRM, you need to create another Zap. In the same way, as with the first Zap, you will also need to look up the profile first and only then, record a message. Here are the workflows of the most popular CRMs:
Once you add Dux-Soup as your trigger app and ‘New LinkedIn Message’ as the trigger event, you will receive sample test data. Please take note of the ‘fromId’ field:
In your next step, add your CRM as an action app and “Find Record” as an action event. For example:
You will need to connect your CRM account and select LinkedIn ID as your search field. Make sure you use a search value ‘fromId/Profile ID’ in the Search Value field.
Add another action app and select “Create Record” as an action event:
Choose your account and move further to set up a new Task action as Salesforce Object. Make sure you use a Salesforce ID in a name field that can be found in Find Record in the Salesforce option.
Fill in the required fields as you prefer, once your reach a Description field add Data Text and Data URL to the field:
You can now test your Zap and turn it on.
If you want to see the Zapier setup in action, watch this webinar recording where Giles Garnett, Head of Professional Services at Dux-Soup, demonstrates the Zapier integration with Dux-Soup and CRM.
It’s worth mentioning that Dux-Soup Turbo has two native CRM integrations: Hubspot and Pipedrive. Transferring your messages using our native integration is easy super simple! All you have to do is tick these options:
For more integration details:
Our tech team is currently working on new CRM integrations and we are open to your suggestions. Please feel free to add a CRM request or upvote if it's already listed - https://feedback.dux-soup.com/.
How does it work in reality?
To take a look at some of the businesses using these techniques today, visit our LinkedIn automation case studies pages.
Take a look at our latest lead gen hacks
For more LinkedIn generation tips, take a look at our blogs and webinars.
New to Dux-Soup, how about a Free Trial?
If you'd like to take advantage of the 14 day free Dux-Soup trial, then get started here.
Handle your entire sales pipeline, track your performances, and in the end, close more deals.