Dux-Soup

Queue LinkedIn outreach activity through the Dux-Soup Remote Control API, manage the action queue, and read prospect conversations and tags. Agents pace outreach against real limits instead of tripping them.

27 actions Custom auth available

Dux-Soup website ↗ Capability data verified 2026-08-02

A scheduled refresh of a saved LinkedIn search returns a new set of profiles

Agent confirms the Dux-Soup account is reachable and correctly identified with Get User Profile

Agent reads the account's configured invitation and visit behaviour with Get Settings

Agent measures the existing backlog with Get Queue Size and inspects what is already committed with Get Queue Items

Agent applies segmentation tags to the new prospects with Add Prospect Tags, which takes effect immediately rather than joining the queue

Agent reports the proposed enrollment count next to the work already waiting to run

The operator approves, trims or defers the batch before Batch Enroll commits days of activity to their own browser

What This Integration Enables

Dux-Soup is not a cloud sending platform, and building a workflow that pretends otherwise is the fastest way to get it wrong. It is a Remote Control API for software that runs on an operator's own machine, through their own browser extension or their own cloud agent, under their own LinkedIn session. Every activity call is an enqueue. Visit Profile, Send Connection Request, Send Message and the rest return a queued item, not a result, and the work drains later at whatever pace the operator's agent and LinkedIn's own limits allow. That architecture is the point, because it keeps the activity attributable to a real person rather than to a server farm. FlowRunner connectors model it honestly: the queue is a first-class object with Get Queue Size, Get Queue Items and Clear Queue, so a flow can see its own backlog instead of firing into the dark.

What agents get on top of the queue is the rest of the working surface. They can enroll prospects into campaigns one at a time or straight from a search result, read the full conversation history Dux-Soup holds for a profile, manage tags directly without queuing, and read and write more than sixty user settings that govern invitation limits, visit scheduling and message templates. FlowRunner's contribution is the judgment layer around a system whose commitments are hard to recall: because pending work executes under a named person's LinkedIn identity, the decision to add a large amount of it belongs to that person, not to the agent that assembled the list.

Without FlowRunner

Queue depth invisible Nobody checks what is already pending before adding more work

Settings edited by hand Invitation limits and visit scheduling are changed in the extension UI with no record of what changed

All or nothing undo The only way to stop a runaway queue is to empty it entirely and lose the pending work

With FlowRunner

Backlog read before loading The agent measures pending work and reports it before proposing a new batch

Settings read then written The agent reads the full settings object first, changes only named keys, and reloads the extension so the change takes effect

Batch size decided by a person The operator sees the backlog and the proposed addition together, and sets the number

Use Case Scenarios

Pacing outreach against real backlog

An agent sources a fresh cohort each morning and would like to put them into a campaign. Before it queues anything, it calls Get Queue Size scoped to the campaign and to the connection request command type, so it can see exactly how many invitations are already waiting to go out under this account. If the backlog is already several days deep, the agent does not add to it. It tags the new cohort with Add Prospect Tags so nothing is lost, reports the backlog, and holds the enrollment until the queue drains. Pacing stops being a guess about LinkedIn's limits and becomes arithmetic on the queue the operator can actually see.

Warming before asking

For a high-value segment, an agent stages the touches rather than leading with an invitation. It queues Visit Profile so Dux-Soup captures structured profile data, queues Like Post as a light engagement touch, and, a day later, queues Follow Profile, which does not consume the weekly invitation allowance at all. Only after those land does the agent queue Send Connection Request with a note built from the profile data the visit captured. The connection request arrives to someone who has already seen the name twice, and the invitation allowance was spent on a warmer target.

Settings change with a safe read-modify-write

An operations lead wants invitation volume reduced across a team of Dux-Soup accounts ahead of a holiday period. Rather than editing each extension by hand, an agent calls Get Settings on each account to capture the current object, which spans more than sixty values across eight groups. It writes only the named limit keys with Update Settings, then calls Reload Extension so the running agent picks up the new values instead of continuing on stale configuration. Every account ends up on the same policy, and the flow has a record of what it changed and what it left alone.

Human-in-Loop Highlight

Batch Enroll takes an entire LinkedIn search result and pushes every profile in it into a campaign in one call. That single call can commit days of activity to a queue that executes through one person's browser, under one person's LinkedIn session, at a pace nobody controls once it starts. The only reverse gear is Clear Queue, and it is deliberately blunt: it empties the queue entirely, discarding every pending command including work the operator did want, with no way to recover it. So the agent does the arithmetic and stops. It reports the current depth from Get Queue Size, the sample of what is already pending from Get Queue Items, the enrollment cap it proposes, and asks the account owner: "Your queue has 412 items pending, roughly four days of activity at current settings. This search matched 260 more profiles. Enroll all 260, cap at 80, or hold until the queue drains?" The operator answers, because the queue runs on their machine under their name. This is the digital andon cord applied to a system where the undo button is a sledgehammer.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

27 actions

Queued LinkedIn Activity

Visit Profile Queues a profile visit, which captures the profile's structured data and delivers it to any webhook the account has configured. Used as the first low-friction touch in a staged sequence and as the cheapest way to harvest profile fields for personalization.
Enroll In Campaign Queues enrollment of one profile into a Dux-Soup campaign, which then drives that profile through the campaign's own sequence of visits, connection requests and messages. The campaign id is mandatory, so a flow needs to carry it explicitly.
Send Connection Request Queues a connection request, optionally carrying a personalized note. Leave the message empty for a bare invitation. Execution runs through the operator's own agent and is subject to the sending limits configured on the account.
Send Message Queues a direct message to a profile the account is already connected to. Message text is mandatory. Use Send InMail instead when the recipient is not a first-degree connection.
Send InMail Queues an InMail to a profile the account is not connected to. Both a subject and a body are required, and the account must hold InMail credits for the send to succeed, which makes a credit check worth doing upstream.
Tag Profile Queues one or more tags onto a profile inside Dux-Soup. Tags are how profiles are segmented for later filtering and campaign targeting.
Untag Profile Queues removal of named tags from a profile, leaving any tag not in the list intact.
Follow Profile Queues a follow, a lower-friction touch than a connection request that does not consume the weekly invitation allowance. Useful when invitation capacity is the scarce resource.
Disconnect Profile Queues removal of an existing connection. Reconnecting afterwards requires a fresh invitation, so this is not easily reversible and is worth confirming before an agent runs it across a segment.
Endorse Profile Queues skill endorsements on a profile. The count controls how many of the listed skills are endorsed.
Like Post Queues a like on the profile's most recent post, a light engagement touch commonly used to warm a prospect before an invitation.
Save Profile As Lead Queues saving the profile as a lead in LinkedIn Sales Navigator. Requires the account to hold a Sales Navigator subscription.
Save Profile To PDF Queues an export of the profile to PDF, producing a snapshot of the profile as it stands at that moment.

Queue Control

Get Queue Size Returns how many items are waiting in the action queue, optionally narrowed to one campaign, one profile or one command type. Because every activity call is asynchronous, this is the main way to tell whether earlier work has drained and whether there is room for more.
Get Queue Items Returns the items currently waiting, up to one hundred, with the same optional filters. Used to inspect exactly what is pending before proposing a new batch or before clearing anything.
Clear Queue Empties the action queue, discarding every pending command. Work already executed is unaffected, but anything still waiting is lost and must be queued again. This is the only stop mechanism, and it is all or nothing.

Prospect Data

Get Conversation Returns the conversation history Dux-Soup holds for one profile, covering messages, invitations and related events with their raw LinkedIn payloads. Used to reconstruct an exchange before deciding on a follow-up.
Get Prospect Tags Returns every tag on a prospect, including Dux-Soup's own system tags, which are prefixed with a duck emoji so they can be told apart from tags you set yourself.
Add Prospect Tags Adds tags to a prospect directly, bypassing the action queue, so the change takes effect immediately rather than waiting for the agent to run. Existing tags are left in place. This is the right call when a flow needs segmentation to be true right now.
Remove Prospect Tag Removes a single tag from a prospect directly, without going through the queue. Other tags are untouched.

Account and Extension Control

Get User Profile Returns every attribute of the Dux-Soup user profile behind the configured user id. Intended for operators managing several LinkedIn accounts who need to report across them, and useful as a connection smoke test at the top of a flow.
Get Settings Returns all user-configurable settings across the eight groups Dux-Soup exposes, covering more than sixty values including invitation limits, visit scheduling and message templates. Always read this before writing so unrelated values are not disturbed.
Update Settings Writes user-configurable settings without touching the browser extension. Supply only the keys that should change. Pair it with Get Settings to learn the exact key names in use on the account.
Reload Extension Signals the extension to restart and reload its configuration. Use it after writing settings so the running agent picks up the new values, or to recover an agent that has stopped responding.
Bridge Check Forces the message bridge to scan a LinkedIn mailbox for new messages or connections rather than waiting for its own schedule. Choose which box to scan and how many days back to look.
Data Reset Clears the captured profile data held in the browser. Anything already delivered to a webhook or exported is unaffected, but the local cache is emptied and cannot be recovered, so export first if the data still matters.
Batch Enroll Enrolls every profile in a LinkedIn search result into a campaign in one call, with a maximum enrollment cap and a choice of whether the local browser extension or the Dux-Soup cloud agent executes the work. This is the highest-leverage action in the connector and the one that most deserves a person's sign-off.

Frequently Asked Questions

What can FlowRunner do with Dux-Soup?

FlowRunner agents can run Visit Profile, Enroll In Campaign, and Send Connection Request in Dux-Soup, plus 24 more actions.

Does connecting Dux-Soup to FlowRunner require OAuth?

Dux-Soup uses a custom authentication method to connect to FlowRunner.

Can Dux-Soup trigger a FlowRunner workflow automatically?

Dux-Soup doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Dux-Soup

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us