Recently, we updated Dux-Soup in Zapier! Now, you can easily build a 2-way communication channel between Dux-Soup and your existing CRM, a marketing automation tool or more. You can create triggers to link Dux-Soup Turbo with any other external app and record Dux-Soup events to invoke specific behaviour. This opens the door to endless possibilities working with the data you gather from LinkedIn.
In this blog, we’ll show you how you can trigger different LinkedIn events in Zapier and how you can set Dux-Soup to run a certain action on LinkedIn from a different app, like CRM.
Note: you’ll need the Turbo edition for Zapier integration to work. Click, to find out more about Dux-Soup integrations.
After the newest update, the triggers in Zapier can be actual Dux-Soup/LinkedIn events and not webhooks anymore. In order to set Dux-Soup as the trigger app, follow these 5 easy steps:
New Profile Visit Event is triggered when Dux-Soup visits a profile on LinkedIn. If you wish to create a new record in CRM or retrieve an email from the profile, this is the event you need to pick. Find out what data you can scrape using the visit event.
New LinkedIn Message Event triggers the Zap when Dux-Soup detects a newly received message on LinkedIn.
New LinkedIn Connection Event triggers the Zap when Dux-Soup detects a new connection on LinkedIn.
New Dux-Soup Action Event triggers the actions you run on LinkedIn using Dux-Soup; such as ‘connection request’, ‘endorsement’, ‘drip campaign enrollment’, ‘direct message’, etc. For testing, please make sure you select the correct event from the drop-down:
Note: For new connection and message events to be detected, please make sure you enable the Message Bridge in the ‘Options’, ‘Connect’ tab. You can also click on ‘Check Regular’, ‘Check Sales Nav’ and ‘Check Connections’ buttons manually:
Zapier will then show the sample data that Dux-Soup sent. For example:
You can now add the action app. Zapier automates 3,000+ apps in millions of ways and this is one of them!
Note: all actions go to Dux-Dash Queued Activity.
If you don’t set a delay, these actions still go to the queue but are executed immediately unless you have reached the daily limit set in the ‘Options’, ‘Throttling’ tab. Remember, that Dux-Soup executes all automated actions during a profile visit, so the first thing it will look for is the visit limit. If you’re sending connection requests, it will also take into account the connection request limit. Once the daily limit is reached, Dux-Soup will snooze until midnight.
Learn more about daily limits and safety on LinkedIn.
You can find more about the Dux-Soup API on our website. Follow these links to read our API documentation: https://support.dux-soup.com/article/114-webhook-by-example and https://support.dux-soup.com/article/115-remote-control-by-example
Should you have any further questions, feel free to contact Dux-Soup support at info@dux-soup.com and we will be happy to help!
Handle your entire sales pipeline, track your performances, and in the end, close more deals.
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Suspendisse varius enim in eros elementum tristique. Duis cursus, mi quis viverra ornare, eros dolor interdum nulla, ut commodo diam libero vitae erat. Aenean faucibus nibh et justo cursus id rutrum lorem imperdiet. Nunc ut sem vitae risus tristique posuere.