skills/sales-lemlist/SKILL.md
Lemlist platform help — multichannel sequences, lead database, enrichment, Lemwarm, unified inbox, AI personalization, LinkedIn automation, calls, WhatsApp, API, integrations. Use when Lemlist sequences not sending, emails landing in spam despite Lemwarm, leads not importing correctly, integrations not syncing, People Database search returning poor matches, or Lemlist API calls failing. Do NOT use for building prospect lists (use /sales-prospect-list), designing cadence strategy (use /sales-cadence), cross-platform deliverability (use /sales-deliverability), or enriching contacts outside Lemlist (use /sales-enrich).
npx skillsauth add sales-skills/sales sales-lemlistInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Help the user with Lemlist platform questions — from multichannel sequence setup and Lemwarm through lead management, enrichment, AI personalization, LinkedIn automation, unified inbox, API, and integrations.
If references/learnings.md exists, read it first for accumulated knowledge.
Ask the user:
What area of Lemlist do you need help with?
/sales-cadence {your question})What's your role?
What are you trying to accomplish? (describe your specific goal or question)
If the user's request already provides most of this context, skip directly to the relevant step. Lead with your best-effort answer using reasonable assumptions (stated explicitly), then ask only the most critical 1-2 clarifying questions at the end — don't gate your response behind gathering complete context.
Note: If the user needs a specialized skill, route them there with a brief explanation of why that skill is a better fit.
If the request maps to a specialized skill, route:
/sales-prospect-list/sales-enrich/sales-cadence/sales-deliverability/sales-integrationOtherwise, answer directly from platform knowledge using the reference below.
Provide module-by-module guidance based on the user's area:
Core entities — understand these to navigate the UI and work with the API:
| Entity | What it represents | Key relationships | |---|---|---| | Campaign/Sequence | A multichannel outreach sequence | Has Steps, has Leads, uses Email Accounts | | Lead | A contact enrolled in a sequence | Belongs to a Campaign, has activity tracking | | Contact | A person in your database | Can be enrolled in multiple Campaigns | | Company | An organization | Has Contacts, has firmographic data | | Email Account | A connected sending mailbox | Used by Campaigns, has Lemwarm status | | Step | A touchpoint in a sequence (email, LinkedIn, call, WhatsApp) | Belongs to a Campaign | | Schedule | Sending window and timezone config | Associated with Campaigns |
For detailed API documentation including all endpoints, authentication, rate limits, and webhook event payloads, consult references/lemlist-api-reference.md.
Quick reference: Base URL https://api.lemlist.com/api, Basic auth (:apiKey base64-encoded) or Bearer token, rate limit 20 requests per 2 seconds. Key capabilities: campaign CRUD, lead management, sequence steps, enrichment, Lemwarm control, People Database search, inbox/messaging, webhooks.
Always reference references/lemlist-api-reference.md when answering API questions — point the user to it for the full endpoint catalog, request/response schemas, and rate limit details.
Based on the user's specific question:
references/lemlist-api-reference.md."Best-effort from research — review these, especially items about plan-gated features and integration gotchas that may be outdated.
Don't confuse Lemlist's per-seat pricing with unlimited-mailbox tools. Lemlist charges per user/month and limits sending accounts (5 per user on highest plan, $9 per additional inbox). Unlike Instantly or Smartlead which offer unlimited mailboxes on flat-fee plans, Lemlist costs scale with team size and mailbox count. Always check the user's plan before recommending adding more sender accounts.
Don't use "campaign" interchangeably with "sequence." Lemlist calls them "sequences" in the UI and "campaigns" in the API. This inconsistency confuses users. Use "sequence" when discussing the UI and "campaign" when discussing the API. If the user says "campaign," clarify which they mean.
Don't assume LinkedIn steps are available. LinkedIn automation requires the Multichannel Expert plan ($99/user/month). The Email Pro plan ($69/user/month) is email-only. Ask about the user's plan before building multichannel sequences with LinkedIn steps.
Don't skip Lemwarm setup. Lemwarm is free with every seat — there's no reason not to enable it. New accounts without Lemwarm warmup will land in spam. Enable it immediately on every connected email account with at least 30 emails/day warmup volume.
Don't ignore LinkedIn daily limits. Lemlist automates LinkedIn actions but LinkedIn still enforces daily limits. Exceeding ~20-30 connection requests/day or ~50-80 profile visits/day risks LinkedIn account restrictions. Claude tends to suggest aggressive LinkedIn step volumes that exceed safe limits.
Self-improving: If you discover something not covered here, append it to references/learnings.md with today's date.
/sales-cadence — Design outbound cadence strategy (platform-agnostic, works with Lemlist sequences)/sales-deliverability — Cross-platform email deliverability — SPF/DKIM/DMARC, warmup, inbox placement/sales-prospect-list — Build prospect lists to import into Lemlist/sales-enrich — Enrich contacts with emails/phones outside of Lemlist's built-in enrichment/sales-integration — Connect Lemlist to other tools via webhooks, Zapier, or API/sales-mailshake — Mailshake platform help (if using Mailshake instead of Lemlist)/sales-smartlead — Smartlead platform help (if using Smartlead instead of Lemlist)/sales-apollo — Apollo.io platform help (if using Apollo instead of Lemlist)/sales-salesloft — Salesloft platform help (if using Salesloft instead of Lemlist)/sales-do — Not sure which skill to use? The router matches any sales objective to the right skill.User says: "How do I create a multichannel sequence in Lemlist with email and LinkedIn?" Skill does:
User says: "I just connected 3 new email accounts to Lemlist. How do I warm them up?" Skill does:
/sales-deliverability for full domain auth framework
Result: User has Lemwarm running on all 3 accounts with monitoring planUser says: "I want to use the Lemlist API to add leads from our CRM to a sequence" Skill does:
references/lemlist-api-reference.md for full API docsPOST /campaigns/{id}/leads endpoint — email required, custom fields for personalization variablesSymptom: Sequence open rates below 30%
Cause: Insufficient warmup, missing domain authentication, poor sender reputation, or weak subject lines
Solution: Check Lemwarm deliverability score on all email accounts — target 90+ before sequence sends. Verify SPF/DKIM/DMARC in your DNS. Set up a custom tracking domain. A/B test subject lines. See /sales-deliverability for a full diagnosis framework.
Symptom: LinkedIn steps in sequence show as skipped or failed Cause: LinkedIn connection expired, daily limits hit, or user on Email Pro plan (no LinkedIn access) Solution: Verify plan is Multichannel Expert ($99/user/month). Re-authenticate LinkedIn connection in Lemlist settings. Check if daily LinkedIn action limits were exceeded — reduce volume to 20-30 connection requests/day. Verify the lead has a LinkedIn URL in their profile.
Symptom: Waterfall enrichment finding emails for less than 50% of leads
Cause: Leads are in niche industries, use uncommon domains, or have limited public data
Solution: Ensure you're providing name + company (minimum for email lookup). Try supplementing with external enrichment tools (Clay, Apollo, Lusha) via /sales-enrich. For senior executives with low match rates, consider LinkedIn-first outreach instead of email.
tools
Waitlister platform help — pre-launch waitlist platform with hosted landing pages, points-based viral referrals, built-in email broadcasts, REST API, and five HMAC-signed webhook events. Use when choosing Free (100 subscribers) vs Launch $15/mo (unlimited subs, referrals + broadcasts) vs Growth $49/mo (API, webhooks, Klaviyo/Mailchimp/Kit sync, fraud detection unlock here) vs Business $129/mo, building a webhook handler that verifies X-Webhook-Signature, webhooks auto-disabled after 10 consecutive failures, API signups bypassing referral fraud detection because client_ip/fingerprint weren't forwarded, granting bonus points or pulling top referrers via the API for reward fulfillment, broadcast send caps forcing an ESP handoff, automating without Zapier (Waitlister has none — webhooks/API only), or comparing Waitlister vs LaunchList/KickoffLabs/GetWaitlist/Prefinery. Do NOT use for list-growth strategy (use /sales-audience-growth) or LaunchList help (use /sales-launchlist).
development
LaunchList platform help — viral pre-launch waitlist platform with one-time lifetime pricing, gamified referrals (queue jumping, leaderboard, position inflation), embed widget + custom form POST endpoint, new_user/email_verify webhooks, Zapier, and spam protection. Use when choosing Free (100 submissions) vs Launch $29 (500) vs Grow $79 one-time (10K — webhooks, Zapier, team unlock here), wiring waitlist signups into Mailchimp/Kit/HubSpot or a CRM because LaunchList has no email broadcast system, needing programmatic access when there is no public REST API yet (form POST + webhook workaround), building a webhook handler with referred_by referral attribution, blocking disposable-email or bot signups on a viral waitlist, a custom signup form not submitting or not tracking referrals, or comparing LaunchList vs KickoffLabs/Viral Loops/Prefinery/GetWaitlist on one-time vs subscription pricing. Do NOT use for list-growth strategy (use /sales-audience-growth) or KickoffLabs help (use /sales-kickofflabs).
development
UpViral platform help — viral referral marketing and list-building platform (by Emarky) for viral sweepstakes, giveaway/reward campaigns, pre-launch waiting lists, and milestone referrals, with REST API (`app.upviral.com/api/v1/`, form-encoded `uvapikey` + `uvmethod`), Callback-URL webhooks, IP-based fraud detection, and 30+ ESP/CRM integrations. Use when campaigns aren't tracking referral points, deciding between Starter $79/mo (10K leads, NO API) vs Business $119/mo (API + webhooks) vs Premium $319/mo, the API erroring because you're on Starter where API/webhooks are gated, building a pipeline with `add_contact`/`get_leads`/`get_leads_points`, interpreting same-IP suspicious-referral flags, or picking UpViral over Viral Loops/Vyper/Gleam. Do NOT use for newsletter audience growth (use /sales-audience-growth), KickoffLabs help (use /sales-kickofflabs), merge-tag referrals (use /sales-referralkit), SparkLoop recommendations (use /sales-sparkloop), or multi-level Level 1/2/3 tracking (use /sales-referralhero).
tools
ReferralHero platform help — full-stack referral, affiliate, waitlist, contest, and NPS platform with REST API, webhooks, Zapier, native ESP connectors, multi-level referral tracking (Level 1/2/3), coupon groups, anti-fraud, and a 5,000 calls/hour limit. Use when referrals aren't tracking, deciding between Free (no API) vs PRO $199/mo (API + webhooks) vs PREMIUM $399/mo (ReCaptcha + SMS Verification), auth failing with `no_token` or `Bearer` vs `X-API-Key`, Level 2/3 counts off from calling `level_2_all_referrals` not `level_2_referrals`, bulk 429s from not chunking the 500-transaction `add_bulk_transactions` limit, coupon endpoints 404 without a coupon group, reward fulfillment (`promote` then `unlock_promoted_reward`) failing, or comparing to SparkLoop/ReferralKit/GrowSurf. Do NOT use for newsletter audience growth (use /sales-audience-growth), merge-tag referrals (use /sales-referralkit), SparkLoop recommendations (use /sales-sparkloop), or affiliate strategy across tools (use /sales-affiliate-program).