Pipedrive Platinum Partner, top 8 worldwide since July 2026
More than 150 CRM implementations
What we set up with Dux-Soup
Connection to Pipedrive
Connections and replies land in Pipedrive as a person and an activity, with an owner attached.
Dedupe on LinkedIn URL
If the person already exists, only an activity gets added. No second record.
A task per connection
A connection without a task in your CRM is a name on a list. So every connection gets a next step.
Messages that read human
We write the base outreach so you cannot hear the template through it.
A follow-up path
We map what happens after someone connects, and what happens when someone does not reply.
Volumes that protect your account
We keep daily numbers low and only build up once the acceptance rate is healthy.
In short
Dux-Soup in short
Dux-Soup is a Chrome extension that automates actions on LinkedIn: visiting profiles, sending connection requests and sending follow-up messages in a set order. There is also a cloud version. LinkedIn's terms do not allow automation, so keep volumes low. We connect Dux-Soup to Pipedrive, so every connection becomes a person with a follow-up task.
Source: Sales-Surge B.V., based on more than 150 CRM implementations. Dux-Soup Partner, checked on 16 November 2026.
Price
What the Pipedrive integration costs
You hear the price of just the integration after a first call. A full CRM implementation starts from €2,950. You buy the Dux-Soup licence yourself, per user per month. We set up the Pipedrive integration, the dedupe and the follow-up tasks.
Dux-Soup only works on LinkedIn, and any use puts your account at some risk. If your audience is not active on LinkedIn, or you cannot take that risk with your CEO's account, we advise cold email or calling instead.
What does Dux-Soup actually do on LinkedIn?
Dux-Soup carries out the actions a rep would otherwise do by hand. It visits profiles, sends connection requests with a short note and sends follow-up messages once someone accepts. You chain those steps into a sequence with waiting times in between. Dux-Soup calls those drip campaigns.
The standard version works as a Chrome extension. So you need to be logged in to LinkedIn with your browser open. The cloud version runs on a server and keeps going when your laptop is closed. Dux-Soup can also pass its actions on to other systems, and that is exactly where we plug in.
What Dux-Soup does not do: track who owns the next step, create a deal or update your pipeline. You need a CRM for that. Without the integration you end up with hundreds of connections after a month and no idea who to call back.
Is Dux-Soup safe for your LinkedIn account?
Not completely, and we would rather say that up front. LinkedIn's user agreement does not allow automation tools. So any use carries some risk, however careful you are. What you can control is how big that risk is.
LinkedIn caps connection requests per week. At the time of writing that cap sits around one hundred per week for most accounts, but LinkedIn does not publish the exact figure and it changes. These are the guidelines we work with:
Connection requests: start with ten to fifteen per working day. Only build up once more than a third of your requests get accepted.
Pending requests: withdraw requests that are still pending after a few weeks. A long list of open requests stands out.
Profile visits: dozens per day, not hundreds.
Working hours: only let Dux-Soup run on weekdays and within office hours, with random pauses.
New accounts: do not use an account that was just created or has few connections. Start that one by hand.
If LinkedIn sends you a warning, stop completely for a week. Then restart at half the volume. These are guidelines from practice, not a guarantee. LinkedIn decides for itself when to step in.
Dux-Soup, Dripify or Instantly: which one for which job?
Dux-Soup and Dripify are LinkedIn tools, Instantly is a cold email tool. So you are really comparing two channels. The question is not which tool is best, but where your audience spends its time and how personal the first contact needs to be.
Dux-Soup, Dripify or Instantly: which one for which job?
Dux-Soup
Dripify
Instantly
Channel
Dux-SoupLinkedIn
DripifyLinkedIn
InstantlyEmail
Where it runs
Dux-SoupChrome extension, plus a cloud version
DripifyIn the cloud
InstantlyIn the cloud
Fits
Dux-SoupA rep building their own network
DripifyTeams managing several LinkedIn accounts centrally
InstantlyLarger prospect lists who live in their inbox
Watch out for
Dux-SoupLinkedIn limits and the risk to your account
DripifyThe same LinkedIn limits
InstantlyDomain warm-up and the rules for business email
Pipedrive integration
Dux-SoupThrough webhook and Make
DripifyThrough webhook or an integration tool
InstantlyThrough Make, see our Instantly page
In practice we often run LinkedIn and email side by side. Dux-Soup for the personal first touch with decision makers, Instantly for the wider list and Apollo for the data. Pipedrive tracks which channel made contact, so a prospect does not get a first message on two channels at once. How we build that stack is on the page about the outbound sales funnel.
How Dux-Soup gets into Pipedrive
Dux-Soup sends every action out through a webhook. We catch it in Make and write only what your team needs into Pipedrive. The order is always the same:
1. Dedupe on LinkedIn URL. First we check Pipedrive for a person with the same LinkedIn URL. If there is none, we search on name and company. Only when both come up empty do we create a new person.
2. The fields. Name, job title, company, LinkedIn URL, the source (Dux-Soup) and the campaign name. Nothing more. Every field nobody uses makes your CRM slower to read.
3. The activity. An accepted request or a reply becomes an activity on the person, with the message text in it. So a colleague sees what has already been said.
4. The follow-up task. The person's owner gets a task due within two working days. If someone replies positively, we turn it into a lead or deal in the right stage.
An accepted request is not a lead yet. That is why we only create a deal once there is a real conversation. For more on Make as the glue, read Make and Pipedrive.
What we do not do with Dux-Soup
No LinkedIn spam factory
We do not build a LinkedIn spam factory, because it costs you your name and possibly your account. We also do not start a campaign without follow-up in your pipeline. And we do not run campaigns on the account of someone who does not know about it.
Frequently asked questions about Dux-Soup
What is Dux-Soup?
Dux-Soup is a tool that automates actions on LinkedIn: visiting profiles, sending connection requests and sending follow-up messages in a set order. The standard version runs as a Chrome extension in your browser while you are logged in to LinkedIn. There is also a cloud version that keeps running when your laptop is off. It is an outreach tool, not a CRM, so the follow-up has to land somewhere else.
How much does Dux-Soup cost?
Dux-Soup sells a licence per user per month, in several tiers. The bigger tiers include drip campaigns, webhooks and the cloud version, among other things. We do not list amounts here because they change. Check the Dux-Soup website for the current price. You hear the price of our Pipedrive integration after a first call. A full CRM implementation starts from €2,950.
How many connection requests per week can I send safely?
LinkedIn caps connection requests per week. At the time of writing that cap sits around one hundred per week for most accounts, but LinkedIn does not publish the exact number. Our rule of thumb: start with ten to fifteen per working day and only build up once your acceptance rate is healthy. No limit is truly safe, because LinkedIn's terms do not allow automation.
How do you connect Dux-Soup to Pipedrive?
Dux-Soup can send every action out through a webhook. We catch that in Make and write it to Pipedrive. First we check on LinkedIn URL whether the person already exists. If they do, only an activity is added. If they are new, we create the person and organisation. The owner gets a follow-up task with a due date.
What is the difference between Dux-Soup and Dripify?
Both automate LinkedIn outreach with sequences of visits, requests and messages. Dripify runs entirely in the cloud and is built around team campaigns. Dux-Soup started as a Chrome extension and also offers a cloud version. For follow-up in Pipedrive it matters little which one you pick. The work is in what happens after someone accepts.
When do you pick Dux-Soup over cold email?
When your audience is active on LinkedIn and you want a personal first contact. If your audience mostly works from the inbox, cold email through Instantly fits better. We often run both, with Pipedrive as the place where you see per prospect which channel made contact and who owns the next step.
Can I start with Dux-Soup myself?
Yes. Through the Dux-Soup logo at the top of this page you buy a licence with our partner link. Most people manage to install the extension and launch a first campaign on their own. Where it usually breaks is what happens next: connections that land nowhere. If you want us to connect Dux-Soup to Pipedrive, book a call.
What Dux-Soup is, how safe it is for your LinkedIn account, how it compares to Dripify and how every connection lands in Pipedrive with a follow-up task.