Resources · Zapier integration

Dux-Soup Zapier integrationAutomate Dux-Soup with Zapier.

The Dux-Soup Zapier integration gives you 4 triggers and 11 actions, with no searches. All four triggers are instant, so LinkedIn events reach your Zaps right away on any plan. Below: what each one does, what it costs and where it goes wrong.

See the 15 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Dux-Soup Zapier integration changes in your LinkedIn outreach

Dux-Soup automates LinkedIn prospecting: finding leads and engaging with them. Plugged into Zapier, its LinkedIn events can start an automation, called a Zap, and a Zap can hand Dux-Soup new jobs to run: connect, message, visit, tag, enroll in a campaign and more.

One thing to get right before anything else: every Dux-Soup action on Zapier adds a job to the Dux-Soup activity queue. Zapier does not message or connect on LinkedIn itself. Dux-Soup carries out the job when it works through its queue, and the trigger New Dux-Soup Action Event tells you when a queued job actually ran.

With that in mind, three outcomes cover most setups. A follow-up that never forgets: New LinkedIn Connection Event feeds Message Profile or Enroll Profile, so each accepted invite gets its next step. A warm-lead radar: New Profile Visit Event and New LinkedIn Message Event push signals into the rest of your process. A tidy prospect base: Tag Profile and Save Profile as Lead sort people as they move.

What it does not do: there is no search step, so a Zap cannot look up a profile in Dux-Soup first. Every action needs a LinkedIn profile URL handed to it, and some only accept a Sales Navigator one. Nothing that happened before the Zap went live gets picked up.

Data read on 1 October 2026 from version DuxsoupremotecontrolCLIAPI@1.3.2 of the app. Comparing tools first? Our n8n vs Zapier page lays the criteria out.

Vocabulary

Zapier vocabulary, in plain English

Seven words do the heavy lifting on this page. Here they are once.

Zap
The automation you build: one trigger, then one or more actions that run each time that trigger event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is switched on, Zapier waits for it.
Action
What the Zap does once started: the step that writes, sends or changes something for you in an app.
Task
The unit Zapier bills: one action that completes successfully. Your plan counts those and nothing else.
Polling vs instant
Polling: Zapier checks the app on a timer. Instant: the app calls Zapier itself the moment the event happens.
Filter
A step that lets the Zap go on only when what arrived meets your condition, and stops it otherwise.
Connection
Your Dux-Soup account linked to Zapier once, then reused by every step that uses Dux-Soup.
Cost

What a Dux-Soup Zap really costs

Dux-Soup is not a premium app on Zapier, so it runs on the free plan. Triggers never cost a task, and Zapier listening for events costs nothing either.

  • Free tasks per month100
  • Steps on the free plan2 (trigger + action)
  • Premium appNo
  • Dux-Soup triggers on a timerNone, all 4 are instant

You pay in tasks: one per action that succeeds. Queuing a message through Message Profile is one task, queuing a tag plus a message is two. An action that fails is not counted. The free plan gives you 100 tasks a month and two-step Zaps only, one trigger and one action. A filter or a second action makes the Zap multi-step, which needs a paid plan. A few apps and actions use more than one task each.

Connect

Connect Dux-Soup to Zapier

  1. 01

    Start from Apps

    In your Zapier account, open Apps and click + Add connection. A connection is your Dux-Soup account linked once, then reused by every Zap step that talks to Dux-Soup.

  2. 02

    Select Dux-Soup

    Search for Dux-Soup in the dialog, pick it and click Add connection. You need a Dux-Soup account, plus access to anything you do not own that the Zap should act on.

  3. 03

    Sign in and allow access

    A new tab opens. Sign in to Dux-Soup with the account whose queue the Zap should feed, then grant Zapier access. From then on, any Zap can pick this connection.

First Zap

Your first Dux-Soup Zap: tag and message every new connection

GoalWhen someone accepts your LinkedIn invite, tag the profile and queue a welcome message in Dux-Soup.

  1. 01

    Build: pick the trigger

    Start a new Zap, choose Dux-Soup as the app and New LinkedIn Connection Event as the event, then select your Dux-Soup connection.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent connection events from your account, so you can map the next steps from a real profile.

  3. 03

    Build: queue a tag

    Add Dux-Soup as an action, choose Tag Profile, map the profile URL from the test result and type the tags, separated by commas.

  4. 04

    Build: queue the message

    Add a second Dux-Soup action, Message Profile. Map the same profile URL and write the message template you want Dux-Soup to send.

  5. 05

    Test, then Publish

    Test each action and check that the jobs show up in your Dux-Soup queue. Then click Publish. Two actions make it multi-step, so this one needs a paid plan.

Triggers

Dux-Soup triggers: what starts a Zap

4 events start a Zap when something happens in Dux-Soup, and 4 of them are instant: the app calls Zapier straight away, whatever your plan.

1

New Dux-Soup Action Event

Instant trigger

In Zapier“Trigger when a queued action executes.”

Fires when a job sitting in your Dux-Soup queue actually gets executed. It is the confirmation signal: the action you queued, from a Zap or by hand, has now run on LinkedIn.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a recruiter wants a log of every connection request that really went out, not just the ones that were planned.
Watch out
if this Zap queues new Dux-Soup actions, each executed job triggers it again, and you have built a loop.
2

New LinkedIn Connection Event

Instant trigger

In Zapier“Trigger when a connection has been added.”

Starts the Zap each time a new connection is added to your LinkedIn network. Zapier highlights it as one of the app's key triggers, and it is the natural start of any follow-up sequence.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a SaaS founder wants every accepted invite to get a thank-you message queued the same day.
Watch out
only connections added after the Zap is published come through, never your existing network.
3

New LinkedIn Message Event

Instant trigger

In Zapier“Trigger when a new message is received.”

Runs whenever a new LinkedIn message is received. For anyone doing outbound, a reply is the moment that matters most, and this trigger catches it without you watching the inbox.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a consultant tags every prospect who answers so replies never sit unread in a crowded inbox.
Watch out
a Zap that answers with Message Profile can set off a back-and-forth if the other side also automates, so add a filter.
4

New Profile Visit Event

Instant trigger

In Zapier“Trigger when a new visit event is added.”

Each new profile visit event added in Dux-Soup starts the Zap. It turns visits into something your process can act on, instead of a list you scroll through later.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
an agency owner wants each visited profile tagged so the team knows who was already looked at.
Watch out
pairing it with the Visit Profile action makes every queued visit trigger the Zap again, which loops fast and burns tasks.
Actions

Dux-Soup actions: what a Zap can queue

Dux-Soup gives you 11 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Connect Profile

Action

In Zapier“Add a Connection Request action to the activity queue.”

Puts a connection request into the Dux-Soup queue for the profile URL you give it. Dux-Soup sends it when it reaches the job.

When to use it
a webinar attendee shares a LinkedIn URL in your form, and you want an invite to follow.
Watch out
the optional force setting ignores all your exclusion rules, so leave it off unless you mean it.
2

Disconnect Profile

Action

In Zapier“Add a Disconnection action to the activity queue.”

Queues the removal of a connection with a profile, the reverse of Connect Profile.

When to use it
trim connections you flagged as irrelevant during a network clean-up.
Watch out
test it on a profile you really want gone, because a wrong mapping targets the wrong person.
3

Endorse Profile

Action

In Zapier“Add a Profile Endorse action to the activity queue.”

Queues an endorsement on a profile, a light-touch way to get noticed by someone.

When to use it
endorse long-standing clients after a project closes, as a quiet thank-you.
Watch out
like Follow, it needs a regular LinkedIn profile URL, and a Sales Navigator link will not do.
4

Enroll Profile

Action

In Zapier“Queue action to enroll a profile into a Campaign.”

Queues the enrollment of a profile into a Dux-Soup campaign, from the profile URL you map.

When to use it
push every new lead from your form straight into a nurture campaign.
Watch out
the force setting skips your exclusion rules, which can enroll people you meant to keep out.
5

Follow Profile

Action

In Zapier“Add a Profile Follow action to the activity queue.”

Queues a follow on a profile. The field asks for a regular LinkedIn profile URL, and the force setting is there as on most actions.

When to use it
follow speakers from an event before reaching out, to warm things up.
Watch out
it expects a regular LinkedIn profile URL, not a Sales Navigator one.
6

InMail Profile

Action

In Zapier“Queue action to send a message to a profile using InMail.”

Queues an InMail to a profile, with a subject and a message template of your choice.

When to use it
reach decision makers outside your network after they appear in a target account list.
Watch out
the target URL must be a Sales Navigator profile URL, and the subject and template are both required as well.
7

Message Profile

Action

In Zapier“Add a Direct Message action to the activity queue.”

Queues a direct message to a profile, built from the message template you write in the step.

When to use it
thank each new connection with a short note that mentions how you met.
Watch out
both the profile URL and the message template are required, so a missing value stops the step before Dux-Soup sees anything.
8

Save Profile as Lead

Action

In Zapier“Add a Profile SaveAsLead action to the activity queue.”

Queues a SaveAsLead job on a profile, which Dux-Soup runs from its activity queue like every other action.

When to use it
save every visitor from a target industry as a lead so your reps pick them up.
Watch out
it works with Sales Navigator profile URLs only, so a regular LinkedIn link fails here.
9

Save Profile to PDF

Action

In Zapier“Add a Profile SaveToPDF action to the activity queue.”

Queues a PDF export of a profile, handy when you want a copy of it outside LinkedIn.

When to use it
keep a snapshot of a candidate's profile at the moment they applied.
Watch out
it takes a regular LinkedIn profile URL. Force is optional here too.
10

Tag Profile

Action

In Zapier“Add a Profile Tag action to the activity queue.”

Queues tags on a profile in Dux-Soup, so you can sort and segment people later.

When to use it
tag everyone who replied so the team knows who is in conversation.
Watch out
tags go in one field separated by commas, and both the URL and the tags are required.
11

Visit Profile

Action

In Zapier“Add a Profile Visit action to the activity queue.”

Queues a visit to a profile. The profile URL is the only field it needs, which makes it the simplest action of the list.

When to use it
visit a prospect's profile right after they download your guide.
Watch out
do not pair it with New Profile Visit Event in the same Zap, or every visit restarts it.
When it breaks

When a Dux-Soup Zap breaks

Zapier attaches no help article to Dux-Soup and lists no limit specific to it. What breaks is the general behaviour of Zaps, and a LinkedIn tool hits those edges quickly.

Four cases show up most often with this app. If one of them has you stuck, our Zapier troubleshooting service is there for it.

  • The Zap loops on itself

    Visit Profile feeding New Profile Visit Event, or any queued action feeding New Dux-Soup Action Event: each run triggers the next. Tasks vanish. A filter breaks the cycle.

  • Your existing network is ignored

    A Zap only reacts to what happens after it is published. Connections, messages and visits from before stay out. Handling the backlog is a separate job.

  • A big batch gets held back

    When a trigger suddenly returns a large batch, after a bulk campaign for instance, Zapier's flood protection can hold the Zap back rather than run it for every item.

  • The wrong kind of profile URL

    A Sales Navigator link in Follow, or a regular one in InMail, makes the action fail. Failed actions cost no task, but the job never reaches the queue.
Need help

Need help automating Dux-Soup with Zapier?

A person reads every message.

FAQ

Dux-Soup Zapier integration: frequent questions

01Is the Dux-Soup Zapier integration free?
Yes, on the Zapier side. Dux-Soup is not a premium app, so it connects on the free plan. That plan gives you 100 tasks a month and Zaps of two steps: one trigger and one action. A connection event that queues one message fits. Add a filter or a second action, such as tagging before messaging, and the Zap becomes multi-step, which needs a paid plan. Plan for that early if your sequences have more than one step.
02How many Zapier tasks does a Dux-Soup Zap use?
One task per action that succeeds, each time the Zap runs. The trigger is free, and so is Zapier listening for LinkedIn events. A Zap that tags a profile and queues a message uses two tasks per new connection. If an action fails, for example because the profile URL is the wrong kind, it is not counted. Some apps and actions take more than one task, so check the task history after the first runs.
03Does Dux-Soup trigger Zaps in real time?
Yes. All four Dux-Soup triggers are instant: New Dux-Soup Action Event, New LinkedIn Connection Event, New LinkedIn Message Event and New Profile Visit Event. Dux-Soup notifies Zapier as the event happens, so the Zap starts right away on every plan, including the free one. The polling grid (15 minutes on Free, 2 on Professional, 1 on Team and Enterprise) does not apply. The actions are a different story: they join the Dux-Soup queue and run when Dux-Soup gets to them.
04What does it take to connect Dux-Soup to Zapier?
A Dux-Soup account, plus access to anything you do not own that the Zap should touch. In Zapier, open Apps, click + Add connection, search for Dux-Soup and click Add connection. A tab opens where you sign in to Dux-Soup and grant Zapier access. The connection is then available in all your Zaps. Use the account whose activity queue should receive the jobs, since every action lands there. You only do this once.
05Why does a Dux-Soup action fail on the profile URL?
Because the field wants a specific kind of URL. Every Dux-Soup action requires a profile URL, and the labels spell out which one. InMail Profile and Save Profile as Lead accept Sales Navigator URLs only. Endorse Profile, Follow Profile and Save Profile to PDF expect a regular LinkedIn URL. Map the wrong kind and the step fails. The task is not charged, but the job never reaches your queue, so test each action once.
06What if the Dux-Soup operation you need is not listed?
Combine what exists first. A trigger plus a filter plus one of the eleven queue actions covers most outreach sequences that look missing at first sight. There is no search step for this app, so a Zap cannot look a profile up inside Dux-Soup before acting. The notes on this page follow what the Zapier editor offered on 1 October 2026. If your need still falls outside, compare automation platforms before you build around a gap.
07Zapier, Make or n8n for Dux-Soup?
Choose on criteria, not on a ranking. On Zapier, Dux-Soup brings four instant triggers and eleven queue actions and runs on the free plan, which suits someone who wants LinkedIn signals flowing without code. The cost is one task per successful action, and anything beyond two steps needs a paid plan. If your sequences chain several actions per profile, compare how each platform counts usage. Start small and read the task history first.
Same platform

Other docs you might need on this stack.

Browse all integrations