Moosend
Integrations › Moosend

Moosend Integration

Add ad leads to Moosend mailing lists automatically with name, email, phone, and custom fields mapped -- so your automation workflows trigger instantly.

Available Integrations

Connect Moosend with 4 lead sources

Start Free Trial No credit card required · 14-day free trial
Trusted by
1,000+ businesses
Leads synced
2M+
Integrations
37+
Free trial
14 days, no card

How It Works

1
Connect Your Ad Account
Link your Facebook, Google, LinkedIn, or TikTok ad account to LeadSync in one click.
2
Choose Moosend
Select Moosend as your destination and authenticate your account.
3
Map Your Fields
Match your lead form fields to Moosend and start syncing leads instantly.

How LeadSync Subscribes Leads to a Moosend Mailing List

Moosend's API at api.moosend.com/v3/ uses your account API key as a query-string parameter (?apikey=...) rather than a header, and every endpoint returns its payload wrapped in a {Context: ...} envelope. LeadSync handles both quirks transparently -- you paste a single API key into the connection settings and the integration calls GET lists.json to enumerate every MailingList on your account so you can pick the destination for each lead source.

Each new Facebook, Google, LinkedIn, or TikTok lead is then a single POST to subscribers/{listId}/subscribe.json with the standard fields (Name, Email, Mobile) on the top-level payload and any custom fields appended to the CustomFields array as Name=Value strings -- the format Moosend's subscribe endpoint expects.

List-Scoped Custom Fields and the Required Email

A subtle Moosend behaviour worth knowing: custom fields are defined per list rather than per account. So the field schema LeadSync's mapping screen shows you depends on which destination list you picked -- LeadSync calls lists/{listId}/details.json live, reads the CustomFieldsDefinition array, and surfaces every field defined on that specific list (with required fields flagged with an asterisk).

Switching the destination list mid-setup refreshes the field schema accordingly. The Email field is always required and uses an internal DEFAULT:Email identifier that LeadSync hoists onto the top-level Email key of the subscribe payload; DEFAULT:Name and DEFAULT:Mobile follow the same convention. You won't see the DEFAULT: prefix in the UI -- only inside Moosend API logs.

Triggering Moosend Automation Workflows

Moosend's automation workflows can use "member added to a list" as a trigger condition, which is the cleanest way to wire up paid-social welcome flows. Build a workflow in Moosend, point it at the list LeadSync writes to, and every new lead enters the workflow within seconds of submitting the ad form -- triggering welcome emails, drip sequences, conditional branching by custom field value, or behaviour-based segmentation.

For multi-source attribution, run one LeadSync connection per ad platform and point each one at a separate Moosend list. Facebook leads can drive a paid-social workflow in their own list while LinkedIn leads run a B2B nurture workflow elsewhere. Each list keeps its own custom-field schema, its own automation, and its own engagement reports -- which means clean attribution across the funnel without cross-channel contamination.

Frequently Asked Questions

In Moosend, open Account > API Key (or Profile > API). Copy the key and paste it into LeadSync when adding Moosend as a destination. LeadSync stores it encrypted and uses it as the apikey query parameter on every api.moosend.com/v3/ request.
It's a Moosend design choice -- each mailing list has its own custom-field schema, defined when you create or edit the list. LeadSync follows the same model: when you pick a destination list in the connection settings, the field mapping dropdown is populated by calling Moosend's lists/{id}/details.json endpoint live and reading the CustomFieldsDefinition array for that specific list.
No. Moosend upserts subscribers by email address within a list, so a repeat submission updates the existing subscriber's field values rather than creating a duplicate row. Your list size and engagement reporting stay accurate.
Required custom fields appear in the LeadSync field mapping dropdown with an asterisk suffix (e.g. "Phone Number*"). LeadSync reads the IsRequired flag from Moosend's CustomFieldsDefinition and surfaces it in the UI so you can see at a glance which fields must have a lead form mapping.
Yes. Build the workflow with a "member added to a list" trigger and point it at the list LeadSync writes to. Every new lead enters the workflow within seconds, ready for welcome sequences, drip campaigns, or behaviour-based branching.
They use special internal identifiers (DEFAULT:Name, DEFAULT:Mobile) that LeadSync hoists onto the top-level Name and Mobile keys of the subscribe payload Moosend expects. Custom fields go into a CustomFields array as Name=Value strings. You won't see the DEFAULT prefix in the UI -- LeadSync handles the conversion automatically.
Yes. Each LeadSync connection points at one Moosend list, so create separate connections per source. Facebook leads can land in a paid-social-Facebook list with one automation, LinkedIn leads in a B2B list with another. Both connections share the same Moosend API key but write to different lists with different custom-field schemas.
Yes. LeadSync supports Moosend as a destination for lead forms across Facebook, Instagram, Google Ads lead form extensions, LinkedIn Lead Gen Forms, and TikTok Lead Generation. Each source is its own LeadSync connection but they all use the same subscribers/{listId}/subscribe.json endpoint.

Start Syncing Leads to Moosend

Set up your Moosend integration in under 60 seconds. Free 14-day trial, no credit card required.

Start Your Free Trial
No credit card required • Set up in 60 seconds • Cancel anytime