Skip to main content
FlowIQ runs a Model Context Protocol (MCP) server, so an AI assistant can work with your FlowIQ account directly. Ask about your chats, broadcast results, orders or abandoned carts, and, if you allow it, have the assistant prepare broadcasts, tag contacts or update your AI agent’s replies.

Connect Claude or ChatGPT

1

Add a custom connector

In Claude or ChatGPT, open the connector settings and add a custom connector.
2

Paste the address

Use https://mcp.flowiq.live/mcp.
3

Sign in with FlowIQ

Sign in with your FlowIQ login, choose the account to connect, and choose what the assistant may do (see Permissions).

Connect with an API key

MCP clients that support custom headers, such as Claude Code or Cursor, can connect with an API key instead of signing in:
The key selects the organization, exactly as it does for the REST API.

Permissions

Every connection has one or more of three permissions: Automations (flows) send messages on their own, so creating or changing one needs both send and write.
  • Signing in connects with read only, unless you tick more on the consent screen. Organization members can grant read only; admins can grant all three.
  • API keys made in the dashboard for an integration have all three. A key can carry fewer, and then it is limited the same way on the REST API: a call outside its permissions gets 403 (see Key permissions).
Sends, broadcasts and changes to your AI agent’s replies happen in two steps: the assistant first shows you a preview (for a broadcast, including how many people it will reach) and only acts after you confirm. A sent WhatsApp message can’t be recalled, so read the preview.

Build on the API with an assistant

The connector can also help you write code against the FlowIQ API. In Claude Code, connect by signing in:
Then run /mcp, choose flowiq and sign in with your FlowIQ login (tick write on the consent screen if you want the assistant to make your API key). Now ask something like “Set me up to build on FlowIQ”, or run the /mcp__flowiq__build_on_flowiq prompt. The assistant:
  1. Reads the build guide: the base URL, authentication, the first calls, the WhatsApp rules that break naive code, rate limits, idempotency and webhook signatures, with links to the full reference.
  2. Offers to make an API key. It first asks what your code will do, to choose the key’s permissions with you (read to look things up, send to send messages, write to change data such as contacts). It then shows a preview of what the key can and cannot do, makes the key only after you confirm, and saves it to your project’s .env as FLOWIQ_API_KEY. The key is shown once; FlowIQ keeps only a hash of it.
  3. Looks at your real account (contacts, templates, conversations) with the read tools when it needs data shapes or template names.
Making a key this way needs a signed-in connection with write, by an admin of an organization with API access switched on. A connection that uses an API key cannot make another key. You can see and revoke every key in Settings → Profile → API Keys.
A key can do whatever its permissions allow, on the REST API and in an assistant alike: a key with send can message your customers. Give a key only what your code needs (a dashboard needs read only) and keep it in an environment variable, never in code or commits.
For the full reference while you code, add the docs as a second server: claude mcp add --transport http flowiq-docs https://docs.flowapt.com/mcp. Every page is also available to AI tools through llms.txt.

What you can ask

  • “How many new contacts did we get this week, and how many orders came from WhatsApp?”
  • “How did Tuesday’s broadcast do? Who didn’t receive it and why?”
  • “Show me today’s escalated conversations.”
  • “Which tickets are waiting on a reply from us, and who has each one?”
  • “Show me ticket FLW-261026-001 and everything that happened on it.”
  • “What were the top reasons customers contacted us last month, and which product caused the most?”
  • “Which products are customers asking about most this month?”
  • “Draft a broadcast to everyone tagged vip announcing the winter sale.”
The read-only questions use the same data as the Reporting API, so the numbers match your dashboard and your scheduled reports.