Subscribe profiles scanned by Dux-Soup to a Mailchimp audience

When Dux-Soup scans a LinkedIn profile, FlowMattic adds that person to your Mailchimp audience, or updates them if they are already there, using the profile details you map.

Dux-Soup

Mailchimp

Download this workflow Browse more workflows

2 steps Setup ~5 min Used on 2.2k sites Free to import

What this workflow does

Dux-Soup collects profile data as it works through LinkedIn, but that data is only useful once it reaches the tools you use for follow-up. This workflow sends each scanned profile to a Mailchimp audience, so your prospect list grows alongside your LinkedIn activity.

The Dux-Soup Scan Create trigger fires when Dux-Soup scans a profile and passes along what it captured. The Mailchimp Add New Member step then adds the person to the audience you choose, or updates the member if that email is already there. The step ships unmapped: pick the audience and map the email and name from the scan.

Mailchimp needs an email address, and a LinkedIn scan doesn't always include one. Check what Dux-Soup sends in a test run. Profiles without an email can't be added, and Task History shows Mailchimp's response for each one.

Think about consent too. People you scan haven't signed up for your emails, so keep them in an audience meant for prospects and check the rules where you and your prospects are based before you send campaigns to them.

Prospect list for a sales team

A sales rep scans profiles of people at target companies, and Mailchimp holds them in a prospects audience for a later, permission-based outreach plan.

Recruiters tracking candidates

A recruiter scans candidate profiles with Dux-Soup and keeps the ones with emails in a Mailchimp audience used for job alerts they opted into.

Event follow-up after networking

After a conference, a founder scans the profiles of people they met, so their details sit in Mailchimp ready for an invitation once contact is made.

How this workflow runs

What happens at each step once the workflow is on, and what you need before you import it.

Step 1Trigger
Dux-Soup Scan Create
Fires when Dux-Soup scans a LinkedIn profile. The scanned details, such as the person's name and company, and an email when Dux-Soup has one, become available to map.
Step 2Action
Mailchimp Add New Member
Adds the person to your Mailchimp audience, or updates them if the email already exists there. After import, connect Mailchimp, pick the audience and map the email and name from the scan.

What you need

FlowMatticCore
Dux-Soup AccountAccount
Mailchimp AccountAccount

After importing, map your own data. To keep the template universal, not every step is pre-filled. Open each step in the builder and connect your accounts and fields (channels, lists, sheets, recipients) before you switch the workflow on.

Make it yours

Changes worth making after you import it.

Put a Filter between the Dux-Soup trigger and the Mailchimp step that continues only when the email field is not empty, so profiles without one don't reach Mailchimp.
Map scanned details such as company or job title into Mailchimp merge fields, if Dux-Soup sends them and your audience has matching fields, so you can segment prospects later.
Use a separate Mailchimp audience or a tag for scanned profiles, so they stay apart from people who subscribed themselves.

Questions about this workflow

Does every Dux-Soup scan include an email for Mailchimp?

No. Dux-Soup sends what it found on the profile, and the email may be missing. Check a test run, and use a Filter on the email between the trigger and the Mailchimp step.

What if the scanned person is already in my Mailchimp audience?

The Add New Member step updates the existing member instead of adding a second one.

Is it fine to email people I scanned with Dux-Soup?

That depends on consent and the laws that apply to you and them. Scanned people haven't asked for your emails, so check those rules before any campaign goes to this audience.

Can I use a different Dux-Soup event instead of scans?

Yes. FlowMattic's Dux-Soup integration also has triggers such as Visit Create and Action Create. Swap the trigger and remap the fields.