Skip to content
Skills Library
Sales & customer service · Tool integration

leadmagic-integrations

/leadmagic-integrations

Integrate LeadMagic with GTM platforms — Clay, Apollo, Smartlead, Instantly, Salesforce, HubSpot, Zapier, Make. Bi-directional data flows, webhook enrichment, CRM automation, and verification-at-send patterns. Use when connecting LeadMagic to your GTM stack. Triggers on: "LeadMagic integration", "connect LeadMagic to", "LeadMagic + Clay", "LeadMagic + HubSpot", "LeadMagic + Salesforce", or any platform integration request.

Repository
gtm-skills ↗
Licence
MIT
Last repository change
14.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
8
Scripts
1
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 14.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What to check before installing
  • 1 scripts in this package. Review them before installing, as Claude may execute them.

Scripts: scripts/check-output.py

What it does and when to use it

Integrate LeadMagic with GTM platforms — Clay, Apollo, Smartlead, Instantly, Salesforce, HubSpot, Zapier, Make. Bi-directional data flows, webhook enrichment, CRM automation, and verification-at-send patterns. Use when connecting LeadMagic to your GTM stack. Triggers on: "LeadMagic integration", "connect LeadMagic to", "LeadMagic + Clay", "LeadMagic + HubSpot", "LeadMagic + Salesforce", or any platform integration request.

Triggers from the description

LeadMagic integrationconnect LeadMagic toLeadMagic + ClayLeadMagic + HubSpotLeadMagic + Salesforce
Original author description

Integrate LeadMagic with GTM platforms — Clay, Apollo, Smartlead, Instantly, Salesforce, HubSpot, Zapier, Make. Bi-directional data flows, webhook enrichment, CRM automation, and verification-at-send patterns. Use when connecting LeadMagic to your GTM stack. Triggers on: "LeadMagic integration", "connect LeadMagic to", "LeadMagic + Clay", "LeadMagic + HubSpot", "LeadMagic + Salesforce", or any platform integration request.

How it works

  1. Overview
  2. Authoritative Foundations
  3. When to Use
  4. Platform-Specific Guides
  5. Data Flow Pattern
  6. Common Pitfalls
  7. Output Format
  8. Quality Check
  9. Execution Artifacts
  10. Related Skills
Original SKILL.md headings · 111 lines, 675 words
SKILL.md preview
---
name: leadmagic-integrations
description: >-
  Integrate LeadMagic with GTM platforms — Clay, Apollo, Smartlead, Instantly,
  Salesforce, HubSpot, Zapier, Make. Bi-directional data flows, webhook enrichment,
  CRM automation, and verification-at-send patterns. Use when connecting LeadMagic
  to your GTM stack. Triggers on: "LeadMagic integration", "connect LeadMagic to",
  "LeadMagic + Clay", "LeadMagic + HubSpot", "LeadMagic + Salesforce", or any
  platform integration request.
license: MIT
compatibility: Claude Code, Codex, GitHub Copilot, Cursor, Gemini CLI, OpenCode, Goose, Hermes, Windsurf, Zed
metadata:
  version: "1.1.1"
  author: LeadMagic
  category: leadmagic
  tags: [leadmagic, integrations, clay, smartlead, hubspot, salesforce, zapier]
  frameworks:
    - "LeadMagic docs — Integrations"
    - "Zapier and Make — Trigger/action automation"
    - "Salesforce — Duplicate and matching rules"
  related_skills: [leadmagic-cli, leadmagic-waterfall, crm-integration, clay-automation]
---

# LeadMagic Integrations

## Overview

LeadMagic integrates natively with every major GTM platform. This skill covers
integration setup, data flow patterns, and the verification-at-send principle:
every contact entering a sequence must pass verification first.

## Authoritative Foundations
- **LeadMagic docs — Integrations** — Use the native integrations where they exist before building custom API glue.
- **Zapier and Make — Trigger/action automation** — Build trigger → enrich → write-back flows with error paths and rate-limit-aware scheduling.
- **Salesforce — Duplicate and matching rules** — Match on email and domain before writing enriched records back so enrichment never creates duplicates.

## When to Use

- "Connect LeadMagic to Clay"
- "Integrate LeadMagic with Smartlead"
- "Set up LeadMagic + HubSpot"
- "Push LeadMagic data to Salesforce"
- "Add verification to my Zapier workflow"
- "Connect LeadMagic to Instantly"

## Platform-Specific Guides

### Clay
Native integration. Add LeadMagic Email Finder and Email Validation as
enrichment columns. Configure in conditional waterfalls — LeadMagic first
(verified results), fallbacks for misses. See leadmagic-waterfall skill.

### Apollo
Use LeadMagic Email Validation as a verification step on Apollo-found contacts
before they enter sequences. Apollo finds, LeadMagic verifies.

### Smartlead
Push verified contacts via CLI: `lm integrations smartlead push --campaign <id>`.
Or use API integration. Always verify with LeadMagic before pushing.

### Instantly
Same pattern: verify contacts, then push. `lm integrations instantly push`.
LeadMagic validation ensures bounced emails don't damage sending reputation.

### Salesforce / HubSpot
Enrich CRM records on create or on schedule. Webhook: new contact created →
LeadMagic enrichment → CRM update. Re-verify contacts older than 90 days.

### Zapier / Make
No-code workflows. Trigger: new lead in CRM → LeadMagic enrichment → update
CRM with verified data. Trigger: new form fill → LeadMagic verification →
route to rep.

## Data Flow Pattern

```
Source (CRM, form, list) → LeadMagic enrichment → LeadMagic verification → Send-ready list
```

Always verify between enrichment and send. Platform integration does not
replace the verification step.

## Common Pitfalls

1. **Two-way sync conflicts.** Push from enrichment TO CRM, not both directions.
   CRM-to-enrichment sync creates data conflicts.

2. **No verification before send.** Platform integration handles data movement.
   Verification handles data quality. Both required.

3. **Not using webhooks for real-time.** Batch processing works for lists.
   Webhooks enable real-time enrichment on form fill.


## Output Format

The agent delivers an integration setup guide for the requested platform(s):

- **Integration Configuration:** step-by-step connection setup for the target platform — Clay column config, HubSpot/Salesforce workflow rules, Zapier zap structure, or n8n node sequence with authentication
- **Data Flow Diagram:** plain-text flow showing Source → LeadMagic enrichment → LeadMagic verification → destination system (CRM, sequencer, or webhook)
- **Verification Gate:** explicit before-send confirmation that LeadMagic validation fires before contacts enter any sequence or automation
- **Webhook Setup (if real-time):** endpoint URL format, expected payload schema, success/failure handling, and retry pattern
- **Platform-Specific Pitfall Checklist:** 3–5 integration-specific anti-patterns to avoid (e.g., two-way sync conflicts, skipping the verification step, batch-only when real-time is needed)

## Quality Check

Before delivering, verify:
- [ ] All required sections complete
- [ ] Output matches the user's stated need
- [ ] No vague or unsupported claims
- [ ] Frameworks cited where applicable

## Execution Artifacts

- `references/framework-notes.md` — platform matrix, iPaaS patterns, Eric Clay agency stack
- `templates/output-template.md` — integration config + verify gate deliverable
- `scripts/check-output.py` — local checklist validator for required sections
This skill includes lightweight artifacts the agent can load on demand:
- `references/pat-spielmann-outbound-copy.md` — stack integration + outbound message audit (Pat Spielmann — LeadMagic)
- `references/integration-checklist.md` — go-live checklist per platform (Clay, Smartlead, CRM, n8n)
- `references/waterfall-column-spec.md` — Clay column spec
- the `clay-toolkit` skill — clay-toolkit native integration
- the `smartlead-workflows` skill (clay-enrollment-handoff.md) — sequencer handoff
- `references/gtm-experts-outbound-index.md` — expert router
Use the artifacts when the user asks for an implementation-ready deliverable, a repeatable workflow, or a quality check rather than generic advice.

## Related Skills

- **leadmagic-cli**: CLI-based integration workflows
- **leadmagic-waterfall**: Clay-specific waterfall setup
- **crm-integration**: CRM configuration for enrichment data
- **clay-automation**: Full Clay workflow design
Files in this package (8)
  • SKILL.md 6 KB
  • references/framework-notes.md 1 KB
  • references/gtm-experts-outbound-index.md 7 KB
  • references/integration-checklist.md 2 KB
  • references/pat-spielmann-outbound-copy.md 14 KB
  • references/waterfall-column-spec.md 2 KB
  • scripts/check-output.py 1 KB
  • templates/output-template.md 2 KB

Versions

The database has no other skills named leadmagic-integrations.

Database snapshot: 13.11.2026 · package version 48fc23a3cb2d (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100leadmagic-toolkit
    Complete LeadMagic platform toolkit — API reference, CLI workflows, MCP server setup, enrichment waterfalls, bulk processing, job change detection, and integration patterns. Use when building LeadMagic-powered GTM infrastructure, integrating LeadMagic into…
  • 100leadmagic-cli
    Use the LeadMagic CLI for enrichment automation — find emails, validate contacts, enrich CSVs in batch, find decision-makers by role, and push to outbound platforms (Smartlead, Instantly). Use when automating enrichment from the command line, batch-processing contacts, or…
  • 100crm-integration
    CRM integration patterns for Close CRM, HubSpot, and Salesforce. Use when: Close CRM, HubSpot, Salesforce, CRM API, lead sync, deal sync, activity logging, CRM webhook, pipeline automation, contact enrichment.
  • 100gtm-engineering
    When the user wants to build GTM automation with code, design workflow architectures, use AI agents for GTM tasks, or implement the 'architecture over tools' principle. Also use when the user mentions 'GTM engineering,' 'GTM automation,' 'n8n,' 'Make,' 'Zapier,' 'workflow…
  • 95gtm-engineering
    When the user wants to build GTM automation with code, design workflow architectures, use AI agents for GTM tasks, or implement the 'architecture over tools' principle. Also use when the user mentions 'GTM engineering,' 'GTM automation,' 'n8n,' 'Make,' 'Zapier,' 'workflow…
  • 90clay-gtm-outbound
    Designs, audits and debugs Clay-powered go-to-market workflows: prospecting, signals, enrichment waterfalls, credit control, Functions, Audiences, Workflows, outbound email sequences and sequencer handoff. Use when the user mentions 'Clay,' 'Clay table audit,' 'debug a Clay…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.