Can I send leads to my CRM automatically?

Not with a native connector. Export CSV or Excel, or POST lead events to a URL you control with a Business-plan webhook. That is how most teams push leads into a CRM or middleware today. Native CRM sync is coming soon.

Do I need developers to integrate LeadFormHub?

No for share links and CSV export. Email alerts are on Pro and Business. Webhooks POST a fixed JSON payload to any HTTPS URL on Business—your team or a catch-hook can map fields into the CRM. Customer API keys and a public customer REST API are coming soon.

What does the webhook payload look like?

Each POST body is { event, timestamp, lead }. The lead object includes id, name, email, phone, stage, source, and created_at. Optional HMAC signing uses an x-webhook-signature header when you save a secret.

Integrations

Lead Form Integrations: Webhooks, Email and Exports

Keep verified submissions in one dashboard. Export CSV or Excel on every plan. Email alerts and automation are on Pro and Business. Outbound webhooks with optional HMAC are on Business. Native CRM connectors and Zapier are coming soon—see the webhook docs.

Start Free

What you can connect today

LeadFormHub does not ship native HubSpot, Salesforce, Zoho, or Zapier apps yet. You can still move leads into your CRM by exporting a file or by sending a webhook to a URL your CRM or middleware already accepts.

CSV and Excel export
Available on every plan. Download leads from the dashboard as CSV or XLSX and import them into the CRM or spreadsheet your team already uses.
Email alerts and automation
On Pro and Business, email the account when a lead is submitted, and run rule-based auto-replies or admin emails when a lead is created or changes stage. This uses LeadFormHub email—not a connection to a third-party marketing platform.
Outbound webhooks with optional HMAC
On Business, save an HTTPS URL in Integrations. LeadFormHub POSTs lead.created, lead.stage_changed, and lead.won events. Add an optional secret to sign the body; the signature is sent in the x-webhook-signature header. Full setup notes are in the webhook documentation.

Send leads to your CRM with a webhook

Point a Business-plan webhook at a catch-hook or middleware endpoint your CRM stack already uses. Map lead.name, lead.email, and lead.phone into CRM fields. There is no native CRM connector yet—webhooks are the supported path until native sync ships. For the full decision between a built-in pipeline and form-to-CRM sync, read the CRM form builder guide.

Sample payload

Shape matches buildWebhookPayload in the product code (event, timestamp, lead).

{
  "event": "lead.created",
  "timestamp": "2026-10-16T08:00:00.000Z",
  "lead": {
    "id": "sample-lead-id",
    "name": "Sample Lead",
    "email": "sample@example.com",
    "phone": "+1234567890",
    "stage": "New",
    "source": "Direct",
    "created_at": "2026-10-16T07:59:55.000Z"
  }
}

Coming soon

Native CRM connectors — HubSpot, Zoho, Salesforce, and similar apps are not available yet.
Zapier — there is no LeadFormHub Zapier app, OAuth connection, or pre-built Zap yet.
Customer API keys — no public customer REST API and no API key you can create in the dashboard yet.

Integrations FAQ

Which integrations does LeadFormHub support today?: Every plan can export leads to CSV and Excel. Email alerts and email automation are on Pro and Business. Outbound webhooks with optional HMAC are on Business. Native CRM connectors, customer API keys, and Zapier are coming soon.
Can I send leads to my CRM automatically?: Not with a native connector. Export CSV or Excel, or POST lead events to a URL you control with a Business-plan webhook. That is how most teams push leads into a CRM or middleware today. Native CRM sync is coming soon.
Do I need developers to integrate LeadFormHub?: No for share links and CSV export. Email alerts are on Pro and Business. Webhooks POST a fixed JSON payload to any HTTPS URL on Business—your team or a catch-hook can map fields into the CRM. Customer API keys and a public customer REST API are coming soon.
What does the webhook payload look like?: Each POST body is { event, timestamp, lead }. The lead object includes id, name, email, phone, stage, source, and created_at. Optional HMAC signing uses an x-webhook-signature header when you save a secret.

Need hands-on help? Contact support or read about LeadFormHub. For product steps, see the lead generation form builder.