Integrations, webhooks, and the API

LeadFlow doesn't want to be an island. The Integrations view connects your lead data to the rest of your stack, and there are several layers: outgoing webhooks, inbound webhook receivers, the Zapier/Make integration, and a full REST API plus MCP server for developers.

Outgoing webhooks: send events out

1. 1Open the Integrations view.
2. 2Add a destination — a URL where LeadFlow should POST events.
3. 3Choose which events to send: lead.created, lead.status_changed, lead.won, or quote.created.
4. 4Toggle the destination on and use Test send to confirm your endpoint receives it.
5. 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 a log of incoming events from sources like Typeform, Calendly, Stripe, or a custom source — each normalized into a lead. Use it to pipe form submissions and payment events straight into your pipeline.

Zapier and Make

Connect LeadFlow to thousands of apps through Zapier or Make. The integration exposes triggers (lead created, status changed, lead won) and actions (create lead, update lead), so you can chain LeadFlow into any workflow without writing code.

API keys and the REST API

1. 1Open Settings → API Keys (this area is part of the Business plan).
2. 2Create a key — you'll see the plaintext value exactly once, so copy it somewhere safe.
3. 3Use the key to authenticate requests to the REST API.
4. 4Toggle keys on/off (for example, to rotate access) or delete them.

The MCP server

LeadFlow exposes a Model Context Protocol endpoint for AI assistants. Authenticated with an API key, an AI tool can query your leads, create records, and take actions using the same capabilities as the app — the natural fit for 'agentic' CRM automation.

Next steps

• Review webhook delivery logs in Settings.
• Check plan access to API keys.
• See integrations on the site.