Skip to main content

Connect LeadGenCrypto to CRM

LeadGenCrypto lets you sync verified token project leads into any CRM or sales automation stack. Use this page as the shared pattern that works across Kommo, Salesforce, HubSpot, Zoho, Pipedrive and others. Link it from per-CRM tutorials and onboarding guides.

For API fundamentals, see API Keys and Public API - Quick Reference.

How it works (quick start)​

  1. Create an API key in the app under Settings - API Keys and store it in a secure ENV or secrets manager.
  2. Call the Public API on a schedule (cron, workflow tool or integration platform) to pull new leads into your integration.
  3. Map fields in your CRM so each lead becomes a company/account plus one or more contacts, with wallet and token metadata attached.
  4. Use deterministic dedupe keys (domain, token URL, wallet, primary email) so each project is created once and updated later instead of duplicated.
  5. Respect rate limits from the API Keys page, back off on errors, and keep limit conservative until you are confident in your pipeline.

Integration patterns​

There are two common ways to get data into your CRM.

Option A - Start with CSV imports​

This is the lowest-risk way to validate mappings before you automate:

  1. On the Leads page, use Export - CSV to download a sample of delivered leads.
  2. Import the CSV into your CRM using its native import tool.
  3. Map fields once and confirm that records, owners and pipelines look correct.
  4. Adjust dedupe rules and field mappings until imports behave the way you expect.
  5. When everything looks right, switch to Option B and mirror the same mappings in your API based integration.

Option B - Public API automation (recommended)​

Once mapping is stable, set up a small script or workflow that calls the Public API and upserts into your CRM:

  1. Use a scheduler (cron, serverless, Zapier, Make, n8n or your own worker) to run at or above the minimum interval from the API Keys page.
  2. Call viewRecentLeads for the last 24 hours of leads, or viewLatestLeads with a conservative limit for catch up and backfills.
  3. For each lead in result, derive:
    • Account or Company record from website (domain), tokenUrl, blockchain, tokenSymbol, tokenName.
    • Contact record from email1, email2 and telegram.
    • Wallet or Asset record (optional) from tokenAddress plus blockchain.
  4. Use your dedupe keys (see below) to decide whether to create or update.
  5. Log errors and responses so you can debug rate limiting, invalid keys or mapping issues.

Endpoints you will call​

The same two endpoints power almost every CRM integration.

# Recent (last 24 hours)
curl -G "https://api.leadgencrypto.com/api"   --data-urlencode "module=lead"   --data-urlencode "action=viewRecentLeads"   --data-urlencode "apikey=YOUR_API_KEY"

# Latest (with limit)
curl -G "https://api.leadgencrypto.com/api"   --data-urlencode "module=lead"   --data-urlencode "action=viewLatestLeads"   --data-urlencode "limit=100"   --data-urlencode "apikey=YOUR_API_KEY"
  • Use viewRecentLeads for regular scheduled syncs that run at the minimum interval for your plan.
  • Use viewLatestLeads with a moderate limit for one off backfills, manual catch up and nightly full runs.

Typical fields returned:

createdAt, website, tokenAddress, blockchain, tokenSymbol, tokenName,
tokenUrl, email1, email2, telegram

For details on query parameters and response shape, see Public API - Quick Reference.

Field mapping starter​

Use this as a starting template when configuring CRM field mappings.

  • Account or Company object

    • website (use the domain as the main identity key)
    • tokenUrl
    • blockchain
    • tokenSymbol
    • tokenName

  • Contact object

    • email1 as primary email
    • email2 as secondary email (when present)
    • telegram as a URL or handle field

  • Wallet or Asset object (optional)

    • tokenAddress
    • blockchain

  • Operational fields

    • createdAt as the ingest timestamp in your CRM or data warehouse
    • optional internal fields such as source = LeadGenCrypto, import batch id, script version

Keep field names and types consistent between CSV imports and API based syncs so you can switch between them without surprises.

Your CRM should avoid creating a new record when the same project appears again later. Use deterministic keys where the same real world project always produces the same identifiers.

Good starting keys:

  • Primary domain from website
  • Token URL from tokenUrl
  • Wallet address from tokenAddress (for chains where the token contract is the main identifier)
  • Main email from email1

Suggested rules:

  • For accounts/companies, dedupe primarily on website domain and tokenUrl.
  • For contacts, dedupe on email1 and, secondarily, email2.
  • For wallet or asset objects, dedupe on tokenAddress plus blockchain.

Remember that LeadGenCrypto already avoids re delivering leads to your account with the same primary email or token URL. Your CRM level dedupe is an additional safety net, especially when you merge data from multiple sources.

Scheduling patterns​

Tailor schedule and limit to your plan and CRM.

Light usage or testing

  • Run viewRecentLeads once per day or a few times per week.
  • Use limit 50 to 100 on viewLatestLeads when you need a manual catch up run.
  • Prefer CSV exports for bulk one time imports.

Daily production sync

  • Run viewRecentLeads every 2 to 4 hours on a paid plan, aligned with the minimum interval on your API Keys page.
  • Use createdAt to skip leads you have already processed if your scheduler ever falls behind.
  • Keep limit at or below your Max leads per call.

High volume or multi system sync

  • Use separate API keys per integration (for example, one for Salesforce, one for a data warehouse).
  • Stagger jobs so they do not all run at the exact same minute.
  • Monitor API usage stats and rate limiting on the API Keys page and adjust intervals when needed.

CRMs you can feed from the API​

You can send LeadGenCrypto leads into nearly any modern CRM, either directly or via an integration platform:

  • Kommo CRM - Pipeline centric CRM with native messaging and automation, popular with agencies and solo operators.
  • Salesforce - Enterprise CRM with flexible objects and flows that can model tokens, wallets and projects as separate records.
  • HubSpot - Marketing and sales CRM where you can centralize forms, email and deal pipelines around token projects.
  • Zoho CRM - Highly customizable CRM with free and paid tiers, suitable for small teams and larger orgs.
  • Pipedrive - Simple, pipeline first CRM that works well once you have a clear sales process.
  • Microsoft Dynamics 365 - Enterprise suite tightly integrated with Microsoft 365; good fit for larger operators.
  • monday sales CRM - Board based work management that can combine sales, marketing and ops around one view.
  • Freshsales (Freshworks) - CRM with inbox and telephony integration for outbound heavy teams.
  • Zendesk Sell - Sales CRM aligned with support workflows for orgs already using Zendesk.
  • Keap - CRM plus marketing automation for small businesses and solo founders.
  • Creatio - No code platform where you can design custom workflows on top of CRM data.
  • Less Annoying CRM - Lightweight CRM for small teams that value clarity over complex automations.
  • Insightly - CRM with project delivery features for tracking post sale work.
  • ActiveCampaign - Email automation platform with a built in CRM layer for lifecycle campaigns.
  • Copper - CRM designed for teams that live in Google Workspace.
  • SugarCRM - Mature CRM for marketing, sales and service that can be extended to handle crypto projects.

In every case the pattern is the same: map LeadGenCrypto fields to your CRM objects, define dedupe keys and pick a sync schedule that respects your API limits.

Implementation checklist​

Use this checklist when building or reviewing a CRM integration:

  • API key created and stored in a secure secret store or environment variable.
  • viewRecentLeads and viewLatestLeads tested manually using cURL or a REST client.
  • CSV sample imported into the CRM to confirm mappings before automation.
  • Account, contact and wallet fields mapped, including createdAt.
  • Dedupe rules configured for domain, token URL, wallet and primary email.
  • Scheduler configured at or above the minimum interval from the API Keys page.
  • Logs and alerts in place for invalid api key, rate_limited and other error responses.
  • Backups or exports scheduled in the CRM so you can restore if a mapping is misconfigured.

Troubleshooting​

If your CRM integration is live but results look off:

  • Duplicates in CRM

    • Review your dedupe rules. Make sure domain and token URL are used consistently and emails are normalized (lowercase, trimmed).
    • Check whether multiple systems are creating records from the same API feed.

  • Empty or small batches

    • Confirm that leads are arriving on the Leads page at the expected cadence.
    • Verify that your scheduler is running at the correct interval and time zone.
    • Use viewLatestLeads with a small limit to confirm there are recent leads to pull.

  • Rate limiting or API errors

    • Check per second, daily and minimum interval limits on the API Keys page.
    • Reduce limit, increase the gap between calls or stagger jobs.
    • Rotate the API key if you see invalid api key errors.

For deeper debugging across deposits, plans, filters and API, see Troubleshooting and Tips.