一键在 Manus 中运行任何 Skill

sales-lagrowthmachine

星标58

分支7

更新时间2026年6月28日 11:39

La Growth Machine (lagrowthmachine.com) platform help — multichannel B2B outbound automation across LinkedIn, email, and X: sequenced campaigns (conditions, branches, A-B), per-identity safety limits, waterfall lead enrichment, lookalike + LinkedIn intent signals, a shared inbox, AI copy + AI voice, and outcome tracking. Developer surface: REST API (apiv2.lagrowthmachine.com/flow, apikey query param) to enroll leads into audiences (POST /flow/leads), list campaigns/audiences/identities, and create inbox webhooks for real-time reply events; native HubSpot/Clay/Make/Slack, Zapier/n8n, and an MCP server — API/webhooks gated to the Ultimate plan. Use when enrolling leads via the API, wiring inbox webhooks (create a CRM contact on reply), managing identities/safety limits, building a multichannel sequence, or choosing LGM vs lemlist. Do NOT use for outbound cadence strategy across tools (use /sales-cadence), email deliverability/warmup (use /sales-deliverability), or generic iPaaS wiring (use /sales-integration).

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

sales-skills

sales-skills/sales

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

文件资源管理器

4 个文件

SKILL.md

readonly

同仓库更多 Skills

同仓库

sales-do

sales-skills/sales

Routes any sales, marketing, ad, or GTM objective to the right specialized skill and outputs the install command for that skill plus a ready-to-paste prompt packed with the user's context. Asks clarifying questions when the objective is ambiguous, then hands back a copy-paste-runnable next step. Covers prospecting, outbound cadences, deals, proposals, forecasting, deliverability, enrichment, intent, content, coaching, CRO, SEO, launch directories, newsletters, email/SMS/push marketing, chatbots, influencer marketing, social media, employee advocacy, media relations, reviews, data hygiene, B2B advertising, retargeting, affiliate, loyalty, digital products, memberships, webinars, checkout, and platform-specific help. Use when the user has a sales or marketing question and isn't sure which skill to use, or wants a multi-skill sequence with a batch install command. Do NOT use to solve problems directly — this skill only routes.

2026-06-2858

sales-phantombuster

sales-skills/sales

PhantomBuster (phantombuster.com) platform help — code-free web/LinkedIn automation + scraping + lead-gen: 'Phantoms' (LinkedIn search export, scrapers, auto-connect, email finder), Flows that chain them, AI Agents + a cloud LinkedIn Leads database. Developer surface: a REST API (base phantombuster.com/api/v2, X-Phantombuster-Key-1 header) to launch agents (POST /agent/{id}/launch → container id) and fetch run results (/containers/fetch-result-object), plus the Leads storage and per-agent webhooks (secret param, 11s timeout) on run completion. Billed by execution time + slots; API on all paid plans. Use when launching a Phantom or fetching its scraped output via the API, wiring a run-finished webhook, handling the async agent→container model, managing slots/execution-time, or LinkedIn cookie/safety issues. Do NOT use for prospect-list / lead-sourcing strategy across tools (use /sales-prospect-list), enrichment strategy across vendors (use /sales-enrich), or outbound cadence strategy (use /sales-cadence).

2026-06-2858

sales-prospect-list

sales-skills/sales

Builds targeted B2B prospect lists for outbound campaigns from database providers (Apollo, ZoomInfo, Clay, Cognism). Use when you don't know who to target, your outbound list is too broad and response rates are low, you can't find the right decision-makers at target accounts, your ICP is vague, or your prospect list is full of bad-fit contacts. Do NOT use for enriching existing contacts with emails/phones (use /sales-enrich), interpreting buying signals (use /sales-intent), general Apollo platform help (use /sales-apollo), or hyperlocal / door-to-door / territory / route-based outbound to local SMBs that aren't on databases — restaurants, gas stations, salons, contractors, HVAC — (use /sales-field-sales).

2026-06-2858

sales-intent

sales-skills/sales

Interprets buying signals and prioritize accounts for outreach. Use when drowning in intent data and not sure what matters, can't tell which accounts to prioritize, buying signals aren't translating to pipeline, job change alerts are noisy, intent topics feel too broad, lead scores don't match actual deal quality, or not sure how to act on signals in outreach. Do NOT use for building prospect lists (use /sales-prospect-list), enriching contacts (use /sales-enrich), ZoomInfo-specific intent config (use /sales-zoominfo), or general Apollo platform help (use /sales-apollo).

2026-06-2858

sales-syncgtm

sales-skills/sales

SyncGTM (syncgtm.com) platform help — AI-native GTM data engine that unifies buying signals (job changes, funding, hiring, LinkedIn posts, web-traffic, custom AI signals), waterfall enrichment (verified emails/mobiles, 40+ providers), AI lead scoring (0–100 vs ICP), AI research agents, and a no-code Workflow Builder. Developer surface: an MCP server (api.syncgtm.com/mcp, OAuth browser sign-in, free-plan — works with Claude Code/Cursor to enrich, find emails/phones, read signals), a REST API (api.syncgtm.com, API key), webhooks, and 40+ integrations (HubSpot/Salesforce/Slack/Attio). Use when connecting the MCP server to an AI agent, enriching contacts via the API, acting on buyer signals, scoring leads vs an ICP, building a signal→enrich→outreach workflow, or choosing SyncGTM vs Clay/Trigify. Do NOT use for intent-data strategy across tools (use /sales-intent), prospect-list building (use /sales-prospect-list), or enrichment strategy across vendors (use /sales-enrich).

2026-06-2858

sales-cadence

sales-skills/sales

Designs multi-channel outbound cadences with timing, A/B testing, and content. Use when outbound sequences getting low reply rates, unsure how many touchpoints or what spacing to use, cadence emails sound generic, prospects ignoring calls, A/B tests not moving the needle, sequence performance plateauing, or not sure which channels to include in outreach. Do NOT use for marketing cold email (use /cold-email), automated email flows (use /email-sequence), or general Salesloft platform help (use /sales-salesloft).

2026-06-2858

name	sales-lagrowthmachine
description	La Growth Machine (lagrowthmachine.com) platform help — multichannel B2B outbound automation across LinkedIn, email, and X: sequenced campaigns (conditions, branches, A-B), per-identity safety limits, waterfall lead enrichment, lookalike + LinkedIn intent signals, a shared inbox, AI copy + AI voice, and outcome tracking. Developer surface: REST API (apiv2.lagrowthmachine.com/flow, apikey query param) to enroll leads into audiences (POST /flow/leads), list campaigns/audiences/identities, and create inbox webhooks for real-time reply events; native HubSpot/Clay/Make/Slack, Zapier/n8n, and an MCP server — API/webhooks gated to the Ultimate plan. Use when enrolling leads via the API, wiring inbox webhooks (create a CRM contact on reply), managing identities/safety limits, building a multichannel sequence, or choosing LGM vs lemlist. Do NOT use for outbound cadence strategy across tools (use /sales-cadence), email deliverability/warmup (use /sales-deliverability), or generic iPaaS wiring (use /sales-integration).
argument-hint	[describe what you need help with in La Growth Machine]
license	MIT
version	1.0.0
tags	["sales","outbound","cadence","platform"]
github	https://github.com/lagrowthmachine

La Growth Machine Platform Help

Step 1 — Gather context

If references/learnings.md exists, read it first for accumulated platform knowledge.

What are you trying to do?
- A) Enroll leads into an audience/campaign via the API (POST /flow/leads)
- B) Wire an inbox webhook (e.g. create a CRM contact when a lead replies)
- C) Manage identities + per-account safety limits (LinkedIn safety)
- D) Build/optimize a multichannel sequence (LinkedIn + email + X, conditions, A/B)
- E) Use enrichment / lookalike / intent signals to fill audiences
- F) Sync campaign/lead data out, or decide LGM vs lemlist/Waalaxy
API or no-code? Code → REST API (apikey) + inbox webhooks. No endpoint → native HubSpot/Clay/Make/Slack, Zapier, or n8n.

Skip-ahead rule: if the user's prompt already provides enough context, skip to Step 2.

Step 2 — Route or answer directly

If the question is about...	Route to...
Outbound sequence/cadence strategy across tools (channels, timing, copy)	`/sales-cadence {question}`
Email deliverability / warmup for the email channel	`/sales-deliverability {question}`
LinkedIn outreach strategy / social selling across tools	`/sales-linkedin {question}`
Generic iPaaS wiring to a CRM/other app	`/sales-integration {question}`

When routing, give the exact command, e.g. "This is a strategy question — run: /sales-cadence design a LinkedIn + email multichannel sequence".

Step 3 — La Growth Machine platform reference

Read references/platform-guide.md for the full reference — the identity/audience/campaign/lead model (what's API vs UI), the per-identity safety model, plan tiers (API/webhooks on Ultimate), enrichment/signals, and quick-start recipes (enroll a lead; create an inbox webhook; list campaigns).

Read references/lagrowthmachine-api-reference.md for the integration surface — base https://apiv2.lagrowthmachine.com/flow, apikey query-param auth, the operations (POST /flow/leads to enroll into an audience, Get Campaigns, List Audiences, List Identities, Create/List Inbox Webhooks), the real-time inbox webhook (lead-reply events), native integrations, and the emerging MCP server.

Answer using only the relevant section. Don't dump the full reference.

Step 4 — Actionable guidance

Focus on the user's specific situation:

The write path is enroll-into-audience. POST /flow/leads?apikey=… adds a lead to an audience; a campaign running over that audience then works the lead across channels. You don't "send a message" via API — you enroll, and the sequence executes.
Identities carry the safety limits. Outreach runs through connected identities (LinkedIn/email accounts), each with per-day caps. List/monitor them (List Identities); spreading volume across identities (and not exceeding limits) is how you stay safe — LGM is cloud-based with dedicated proxies.
Inbox webhooks are the real-time hook. Create an inbox webhook to fire when a lead replies (the canonical "create a CRM contact on reply" flow). Treat the URL as secret, dedupe on the lead/message id.
API + webhooks need Ultimate. They're gated to the Ultimate tier (~€150/mo/identity, best-effort) — Basic/Pro may not expose them. Confirm before building.
Enrichment/signals fill audiences. Waterfall enrichment (verified contacts), lookalike, and LinkedIn intent signals auto-import ICP-matching leads — use them to keep audiences fresh rather than manual imports.
Don't confuse channel deliverability with the tool. LGM orchestrates; the email channel still needs warmup/deliverability hygiene — route that to /sales-deliverability.

If you discover a gotcha, workaround, or tip not covered in references/learnings.md, append it there.

Gotchas

Best-effort from research (2026-06) — API/pricing from official docs + integration listings; the Postman collection is JS-rendered so confirm exact JSON in-account.

API key is a query param. ?apikey=… (from Settings → API), not a header — keep it server-side (logs/referrers leak query strings).
API/webhooks are Ultimate-only. Webhooks + advanced integrations are gated to the Ultimate plan; Basic/Pro can't use them. Verify your tier first.
You enroll, you don't send. The API adds leads to an audience; the campaign sequence does the sending. There's no "send LinkedIn message" endpoint — model your flow around enroll + sequence.
Identities have safety limits. Per-account LinkedIn/email caps exist for safety — exceeding them risks the account. Spread across identities; monitor via List Identities.
Webhook signing is undocumented publicly. Treat the inbox-webhook URL as a secret, dedupe on lead/message id, and confirm any signature scheme in the Postman collection.
Endpoint detail lives in Postman. Full per-endpoint JSON/params/rate-limits aren't published outside the (JS-rendered) Postman collection — pull them from there or the help center.
It's LinkedIn-first. LGM's edge is cloud LinkedIn safety + multichannel orchestration; email-first teams may prefer lemlist — compare via /sales-cadence.

Related skills

/sales-cadence — Outbound sequence/cadence strategy across tools (LGM is one of the multichannel platforms covered) — channel mix, timing, copy, tool selection vs lemlist/Waalaxy/Apollo
/sales-linkedin — LinkedIn outreach / social-selling strategy across tools (LGM automates the execution)
/sales-deliverability — Email warmup + inbox placement for LGM's email channel
/sales-integration — Wiring LGM into a CRM via the API / inbox webhooks / Zapier / n8n
/sales-do — Not sure which skill to use? The router matches any sales objective to the right skill. Install: npx skills add sales-skills/sales --skill sales-do -a claude-code

Examples

Example 1: Enroll leads into a campaign via the API (developer/automation)

User says: "When a lead is created in my app, how do I push it into a La Growth Machine campaign automatically?" Skill does: Walks Recipe 1 — POST https://apiv2.lagrowthmachine.com/flow/leads?apikey=YOUR_KEY with the lead fields + the target audience id (get audiences via List Audiences); the campaign running over that audience then works the lead across LinkedIn/email/X. Stresses that you enroll into an audience (there's no send-message endpoint), keeping the apikey server-side, and that the API needs the Ultimate plan. Result: New app leads flow straight into the right multichannel sequence.

Example 2: Create a CRM contact when a lead replies (inbox webhook)

User says: "I want a HubSpot contact created the moment someone replies in La Growth Machine." Skill does: Recommends the native HubSpot integration if it covers it, else the Create Inbox Webhook operation pointing at your endpoint — LGM POSTs the reply event (lead + message); your handler creates the HubSpot contact. Notes treating the URL as secret, deduping on the lead/message id, and that inbox webhooks are Ultimate-tier. Offers Zapier/n8n as a no-code path. Result: Replies become CRM contacts in real time.

Example 3: LGM vs lemlist — which multichannel tool?

User says: "Should I use La Growth Machine or lemlist for outbound?" Skill does: Frames the split — LGM is LinkedIn-first (cloud-based LinkedIn safety since 2017, dedicated proxies, multichannel orchestration, shared inbox), while lemlist is email-first (built-in lead DB, lemwarm warmup, deep email personalization). Recommends LGM when LinkedIn + multichannel is the core, and routes the broader decision: "run: /sales-cadence choose a multichannel outbound tool for a LinkedIn-led motion." Notes pricing is per-identity (Basic €50 → Ultimate €150 with API/webhooks). Result: A grounded tool choice based on channel emphasis.

Troubleshooting

My API calls are unauthorized / 401

Symptom: Requests to apiv2.lagrowthmachine.com/flow/... are rejected. Cause: Missing/invalid apikey query param, or the API isn't enabled on your plan. Solution: Append ?apikey=YOUR_API_KEY (from app.lagrowthmachine.com/settings/api) to every request — it's a query parameter, not a header. Confirm you're on the Ultimate plan (API/webhooks are gated there). Test with a read op like List Identities first.

Leads don't get worked after I add them

Symptom: POST /flow/leads succeeds but no outreach happens. Cause: The lead was added to an audience that no active campaign is running over, the assigned identity is paused/over its safety limit, or required channel data (LinkedIn URL/email) is missing. Solution: Enroll into an audience that a launched campaign targets, verify the identity is connected and under its daily limit (List Identities), and ensure the lead has the channel fields the sequence needs. Enrichment can fill missing contact data.

My LinkedIn account got restricted

Symptom: LinkedIn flags/restricts an identity used by LGM. Cause: Exceeding safe per-day action limits (connections/messages) or aggressive sequences. Solution: Respect the per-identity safety limits (LGM sets them from years of data — don't override upward), warm up new identities slowly, spread volume across identities, and keep sequences human-paced. For channel-mix/volume strategy, use /sales-cadence; for the email side, /sales-deliverability.