| 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.1 |
| 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} |
| 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.
