Dux-Soup runs LinkedIn outreach for you: profile visits, connection requests and message sequences. FlowMattic tells your sales team in Slack when it matters: a prospect replied, a profile that fits your target was scanned, or the robot hit an error or throttle limit. Reps answer warm replies quickly and whoever runs the campaigns knows when one has stopped.
14 triggers 14 actions 6 example workflows 2 ready-made templates Unlimited runs
When this happens in Dux-Soup14 triggers
Do this in Slack14 actions
1. TriggerMessage Received2. ActionSend Channel MessageWhen Dux-Soup fires Message Received, FlowMattic runs Send Channel Message in Slack with the data from that event.
You build this in the FlowMattic workflow builder on your own site. See the setup steps
Each one uses only triggers and actions the two integrations ship today, plus FlowMattic's own tools. Where the library has a ready-made template, import it instead of building from scratch.
Ready-made templateA reply to an outreach sequence is a warm lead. The sales channel gets the prospect's name and message so a rep can answer while the conversation is fresh.
Message ReceivedSend Channel Message
View the template An AI Agent reads each reply and labels it. A Branch posts interested replies to the hot-leads channel and polite refusals to a quiet log, so reps work the promising ones first.
Message ReceivedAI AgentBranchSend Channel Message
A Filter checks the job title and company size of each scanned profile and passes only your target buyers, so the channel shows decision makers rather than every profile Dux-Soup visits.
Scan CreateFilterSend Channel Message
A remote control command that fails can stop a sequence for days. The person running campaigns gets a direct message with the error, so they fix it the same day.
RCComand ErrorSend Direct Message
RCComand Snooze means the robot is waiting because of your throttle settings. A note in the growth channel explains a slow day, so nobody restarts the extension by mistake.
RCComand SnoozeSend Private Channel Message
Teams running several campaigns for different products or clients use a Router on the campaign name, so each reply lands in the channel of the rep or client it belongs to.
Message ReceivedRouterSend Channel Message
Once working, every reply Dux-Soup reads from your LinkedIn inbox is posted to the sales channel.
Open Connects and add Slack with an account that is in the sales channel.
Create a workflow with Dux-Soup's Message Received trigger and follow its instructions to send Dux-Soup events to the workflow.
Ask a colleague to reply to one of your LinkedIn messages and let Dux-Soup read it, so the workflow captures the message fields.
Add Send Channel Message, pick the channel and map the prospect's name, profile link and message. Test it and switch the workflow on.
1. Trigger in Dux-Soup
Message Received
2. Action in Slack
Send Channel Message
Fields mapped from the earlier steps (a typical setup)
| From Dux-Soup | To Slack |
|---|---|
| First and last name | Message: prospect |
| Profile URL | Message: LinkedIn profile |
| Company | Message: company |
| Message text | Message: reply |
A trigger starts a workflow. An action is something FlowMattic does in the app as a step.
Dux-Soup and Slack connect through FlowMattic on your own site, with no separate automation account in the middle and no charge per run.
Reps see responses in Slack instead of in a LinkedIn inbox shared by an outreach robot, so interested prospects hear back.
Errors and throttle pauses reach the campaign owner, so a sequence does not stop quietly for a week.
FlowMattic runs on your WordPress site with unlimited runs, so high-volume profile visits add no per-task cost.
Create a FlowMattic workflow with the Dux-Soup Message Received trigger, add Slack's Send Channel Message and choose the sales channel. Capture a test reply, map the prospect and message into the text and switch the workflow on.
Yes. Add an AI Agent that labels each reply, then a Branch or Filter that passes the interested ones. Everything else can go to a quieter channel or stop.
They are Dux-Soup's remote control events: a command was received, completed, ignored or failed, or the robot is ready or snoozing. Error and Snooze are the most useful to post to the person running campaigns.
Yes. Add a CRM step, such as HubSpot or FluentCRM, to the Scan Create workflow before the Slack message, and post the CRM link with the profile.
Did not find your answer? You can browse the help center or ask us directly.
Slack and Google Sheets149 shared templates
Slack and Airtable44 shared templates
Slack and Fluent Forms42 shared templates
Slack and FluentCRM35 shared templates
Slack and ClickUp28 shared templates
Slack and Fluent Support21 shared templates
Slack and WooCommerce18 shared templates
Slack and Notion17 shared templatesInstall FlowMattic, connect both accounts and import a template. Every run stays on your own server.
30-day money-back guarantee Unlimited workflows and runs Self-hosted
Reviewed 27 Oct 2026. The example workflows are written with AI from the real triggers and actions of both integrations and checked against them. Dux-Soup integration 1.0.0, Slack integration 1.0.
