Three ways your AI talks to Flowpilot.
Pick whichever AI ecosystem fits your team. Or use all three.
In-product AI chat. No setup.
For the SMB owner who wants AI to run the business without context-switching to another tool.
Live in your Flowpilot dashboard. Talk to it in plain English:
- "Send a follow-up to anyone who didn't reply in 3 days"
- "Show me my deals that closed last week"
- "Book the next available slot Thursday for the Tempe lead"
It just does it. No setup, no API keys, no separate subscription.
Claude Desktop, Cursor, Claude Code in 30 seconds.
For the operator who already lives in Claude Desktop or Cursor.
30-second setup: paste your Flowpilot integration URL into your AI tool's settings. Now you can operate your CRM from there:
- "Use Flowpilot to find my contacts named Smith"
- "Have Flowpilot send a test SMS to (555) 123-4567"
- "Show me automations that fired this week"
Works with: Claude Desktop, Claude Code, Cursor, Cline, Continue, Zed, ChatGPT (Custom GPTs with Actions), and any tool that supports the Model Context Protocol.
Direct REST. Scoped fp_* tokens. Full audit log.
For developers, agencies, and enterprise teams.
Direct REST API at app.flowpilot360.com/api/agent/* with scoped fp_*
tokens. Read your pipeline, send messages, fire automations, manage deals — all through your
own scripts, agents, or internal tools.
- Granular scopes (
contacts.read,deals.write,automations.read, etc.) - Full audit log of every action your agents take
- Documented OpenAPI spec, no surprises
- Cross-tenant isolation enforced server-side
Common patterns customers run
- Bring-your-own-agent (BYOA) — your Claude/ChatGPT/internal LLM uses Flowpilot's data the same way your team does. Granular per-token scopes mean one agent can read contacts but never delete them.
- GitHub-driven workflows (Growth+) — connect your repo, and Flowpilot infers your customer journey from your code. Schema changes propose new automations automatically.
- Programmatic onboarding — Zerg pipes Stripe webhooks into Flowpilot to fire lifecycle automations — no custom code required. Your backend can do the same: post lifecycle events directly to the agent API, tags fire automations, no webhooks-in-between.
The Platform Assistant and MCP Server are included on every tier — sign up and you're using them the same day. Agent API requires a paid plan; BYOA tokens are issued from the dashboard.