Integrations, webhooks, and the API
Answer: Outgoing webhooks POST events to a URL you paste (Zapier Catch Hook, Make, Slack). Inbound Typeform/Calendly/Stripe URLs create leads. POST /api/integrations with a Business API key creates or updates a lead. There is no LeadFlow Zapier app.
Send lead events with outgoing webhooks (paste a Catch Hook), receive Typeform/Calendly/Stripe leads, POST create_lead into LeadFlow with a Business API key, and use the REST API plus MCP on Business.
LeadFlow doesn't want to be an island. The Integrations view connects your lead data to the rest of your stack: outgoing webhooks (paste a Catch Hook URL), inbound Typeform/Calendly/Stripe receivers, an inbound POST URL for create_lead/update_lead, and a REST API plus MCP server on Business.
Outgoing webhooks: send events out
- 1Open the Integrations view.
- 2Add a destination — a URL where LeadFlow should POST events.
- 3Choose which events to send: lead.created, lead.status_changed, lead.won, or quote.created.
- 4Toggle the destination on and use Test send to confirm your endpoint receives it.
- 5Check the last status/error per destination so you can see if anything failed.
Inbound webhooks: receive leads from other tools
LeadFlow can also receive data. The Webhooks tab in Settings shows inbound URLs for Typeform, Calendly, Stripe, or a custom source. Those POSTs need a Business API key. Each event is logged as processed, failed, or ignored. Outgoing Catch Hooks on Integrations work on every plan.
Zapier and Make
There is no LeadFlow Zapier app. To send events out, paste a Zapier Catch Hook or Make custom webhook URL into Outgoing webhooks, then choose lead.created, lead.status_changed, lead.won, or quote.created. To send events in, POST create_lead or update_lead to /api/integrations with a Business API key. The URL on the Zapier card is that inbound receiver — it is not a Zapier trigger.
API keys and the REST API
- 1Open Settings → API Keys (this area is part of the Business plan).
- 2Create a key — you'll see the plaintext value exactly once, so copy it somewhere safe.
- 3Use the key to authenticate requests to the REST API.
- 4Toggle keys on/off (for example, to rotate access) or delete them.
The MCP server
LeadFlow exposes a Model Context Protocol endpoint for MCP clients. Authenticate with a Business API key. The 19 CRM tools cover leads, campaigns, quotes, tasks, sequences, competitors, custom fields, and pipeline counts (not win rate, forecast, or ROI) — not Discover, the scoring engine, or send-email. LeadFlow is not an AI-agent product. `enroll_lead_in_sequence` queues a Pro sequence; it does not send.