Home Getting started Connect an AI assistant to Flomixy

Connect an AI assistant to Flomixy

Last updated on Oct 02, 2026

You can let an AI assistant such as Claude work with your account for you. Once connected, you can ask it in plain language to list your connected accounts, write a post, schedule it for a specific time, or show you what is waiting for approval.

The connection uses an API key that you create once and paste into the assistant. This article walks you through it.

What the assistant can do

  • See which accounts and brands are connected.
  • Create posts and drafts, and schedule them for a date and time.
  • Check what is waiting for approval.
  • Upload media and read your best times to post, if you allow it.

Every post the assistant creates waits for human approval by default. Nothing is published until a person on your team approves it. The assistant cannot approve or reject posts itself.

Step 1: Create an API key

Only the workspace owner can create an API key. If you are an admin or a team member, ask your workspace owner to create it for you.

  1. Open Settings → API keys.
  2. Click New API key.
  3. Give the key a name that tells you where it is used, for example "Claude, social team".
  4. Choose the scopes, the permissions the key has. Give the key only what the assistant needs:
    • Posts read / Posts write: see posts, or create, edit and delete them.
    • Accounts read: list your connected accounts and brands.
    • Media read / Media write: browse the media library, or upload files.
    • Schedule read and Analytics read: best times to post, and performance numbers.
  5. Click Read-only first if you just want to look around, then add write permissions later.
  6. Create the key and copy it right away. It is shown only once.

More detail on every scope: API keys: choosing the right permissions.

Step 2: Connect Claude

Claude on the web: sign in with Flomixy (no key)

Only the workspace owner can do this. If you are an admin or team member, ask the owner.

  1. In Claude, open Settings → Connectors and click Add custom connector.
  2. Enter the name "Flomixy" and the address https://mcp.flomixy.com/mcp. Leave any key field empty.
  3. Click Connect, sign in to Flomixy, pick the workspace and click Allow.
  4. Open a new chat and turn the connector on.

Every post Claude creates still waits for approval from a person on your team.

Claude on the web: with an API key

  1. In Claude, open Settings → Connectors and click Add custom connector.
  2. Enter a name, for example "Flomixy", and this address: https://mcp.flomixy.com/mcp
  3. Under authentication, choose No sign-in.
  4. Add a custom header named x-api-key and paste your API key as the value.
  5. Save the connector.
  6. Open a new chat, click the connectors icon and turn the connector on for that chat.

Claude Code

Run this command in your terminal, with your own key in place of ...:

claude mcp add --transport http flomixy https://mcp.flomixy.com/mcp --header "x-api-key: ..."

Then start Claude Code and type /mcp. You should see flomixy in the list as connected.

Using ChatGPT, Gemini, Cursor or n8n, or want to sign in with one click instead of a key? See Connect ChatGPT, Gemini, Cursor and n8n to Flomixy.

Disconnect an assistant

  • Connected with sign-in: open Connected apps in your Flomixy settings and click Revoke next to the assistant.
  • Connected with a key: revoke it in Settings → API keys.

Either way the assistant loses access immediately.

Step 3: Try it

Start with something harmless. Type one of these in the chat:

  1. "List the accounts I have connected."
  2. "Create a post for my Instagram account saying 'Our new menu is here' and schedule it for tomorrow at 10:00."
  3. "Show me which posts are waiting for approval."

The post from example 2 appears in your approvals list. Review and approve it as you would any other post.

Keep it safe

  • Never share your API key: not in chats, screenshots, emails or shared documents. Anyone with the key can act as that key.
  • Use a test account first. Connect a test account and try a few messages before you let the assistant near your real accounts.
  • Revoke a key any time in Settings → API keys. The assistant loses access immediately.
  • Give each tool its own key and only the scopes it needs, so you can revoke one without breaking the others.
  • Be careful about letting an assistant read untrusted content (web pages, emails) while it can post for you. Keep the default of human approval on.

Troubleshooting

  • The assistant says it cannot see the tools. Check the connector is switched on in the chat (Claude on the web) or that /mcp shows it connected (Claude Code).
  • "Unauthorized" or "forbidden" errors. The key was copied wrong, was revoked, or lacks the scope for that action. Create a new key with the right scopes.
  • I do not see Settings → API keys. Only the workspace owner can open it.