Home Getting started

Getting started

By Flomixy Admin
• 13 articles

Getting started: your account and connecting a network

Welcome! This guide walks you through your first steps. Create your account Register with your email and password, or use Continue with Google. The first person who registers for a team becomes its owner; teammates who register later join the existing workspace (an invite or an approval may be required, depending on how your team is set up). Connect a network account Before you click Connect, make sure you're already logged into the account you want (Instagram/Facebook, Threads, LinkedIn, or TikTok) in the same browser. The Connect button hands you off to that network's own login screen, and it uses whichever account is currently signed in there - if you're logged into the wrong account, or logged out, you may end up connecting (or being prompted to connect) the wrong one. If several people share a computer, check the top-right corner of the network's site before you start. 1. Go to Accounts in the sidebar. 2. Click Connect account and choose the network. You will be redirected to that network's own site to sign in and grant access. 3. Approve the requested permissions and you will be sent back - the connected profile appears in the accounts list. Requirements (Instagram): - The Instagram account must be a Business or Creator account (personal profiles cannot publish via the API). - It must be linked to a Facebook Page. - Only workspace owners (and above) can connect or disconnect accounts. Requirements (Facebook): - The Facebook Page must be one you're an admin of; you must be logged into that account in the browser before you click Connect. - Standard "Connect with Facebook" is the normal path and works for most Pages. - If it comes back with no Pages even though you are an admin, your Page's Business Portfolio is different from Flomixy's - use "Or share a Page directly" on the Facebook connection card instead (Business Settings on facebook.com -> Accounts -> Pages -> your Page -> Assign Partner -> paste Flomixy's Business ID -> grant Content access only, not Full control). - Only workspace owners (and above) can connect or disconnect accounts. Requirements (LinkedIn): - Connect uses your personal LinkedIn profile - Flomixy doesn't support posting to LinkedIn Company Pages yet. - Make sure you're logged into the right LinkedIn account in the browser before you click Connect. - Only workspace owners (and above) can connect or disconnect accounts. Requirements (TikTok): - Make sure you're logged into the right TikTok account before you click Connect - TikTok doesn't offer an account picker in the connection window, so it signs in whichever account is currently active in your browser. - TikTok's review of our app is still in progress. Until it's approved, posts publish to TikTok as Only me (visible only to your own account) no matter which privacy option you pick in the composer - we'll show you that before you publish. - Only workspace owners (and above) can connect or disconnect accounts. Requirements (Threads): - Threads uses the same Connect flow as Instagram/Facebook - make sure you're logged into the right account first. - Early access: Threads publishing is still going through Meta's review process, so only a limited number of pre-approved accounts can connect today. If Connect doesn't complete for you, contact us and we'll add your account to the approved list. - Only workspace owners (and above) can connect or disconnect accounts. Connecting Telegram Telegram connects differently from the other networks - there's no login screen. Instead, you add a bot token and chat ID for the channel or group you want to post to. See Connecting your Telegram channel for the step-by-step. Token expiry and reconnecting Access to your Instagram, Threads, Facebook, LinkedIn, or TikTok account is granted through a token that expires periodically. We refresh it automatically, but if it becomes invalid (for example you changed your password or revoked access), the account card shows a Reconnect button. Scheduled posts are paused while the connection is down and resume automatically once you reconnect - nothing is lost. (Telegram doesn't use this kind of token, so this section doesn't apply to it - see the Telegram article above if a Telegram post fails.) Disconnecting or permanently deleting an account If you no longer want Flomixy to publish to an account, open its menu (⋯) on the Accounts page and choose Disconnect. This stops publishing and pauses any scheduled posts aimed at that account - nothing is deleted, and you can reconnect at any time to pick up right where you left off. Once an account has been disconnected, its menu offers a second option: Delete account. This permanently removes the account - and its connection history - from Flomixy. It cannot be undone, which is why it's only available after the account is disconnected, and it's blocked if any scheduled or in-progress posts still target that account (delete or move those posts to a different account first, then try again).

Last updated on Sep 30, 2026

Your home dashboard

Your home dashboard When you sign in, Flomixy opens on your Home dashboard - a single overview of everything happening across your workspace. You can return to it any time from Home in the sidebar. What you'll see Next up - your upcoming scheduled posts, soonest first. Click any post to open it, or select Calendar to see the whole month. Status counters - a quick count of your Drafts, Scheduled, Published, and Failed posts. Click a counter to jump straight to that list. Needs attention - anything that needs a quick fix: - A post that failed to publish - click Fix & retry to open it and try again. - An expired Instagram connection - click Reconnect to link the account again so scheduling and insights resume. Already handled it, or want to hide a note for now? Click the ✕ on the right of the item. It will come back on your next visit if the issue is still unresolved. This week's queue - your weekly posting slots at a glance. Filled slots already have a post; open slots are free - click one to start a post for that time. You manage your slots under Schedule. Approvals - if you review posts, anything waiting for your approval appears here. Click Review to open the approvals page. First time here? A brand-new workspace shows a short setup checklist instead of the dashboard: 1. Connect an Instagram account - link a Business or Creator account. 2. Create your first post - draft a caption, add media, and preview it live. 3. Set up a posting schedule - add weekly slots so queued posts publish automatically. Once your first account is connected, the full dashboard takes over. Related articles - Getting started: your account and connecting Instagram - Scheduling posts and using the calendar - Why did my post fail?

Last updated on Sep 30, 2026

Connecting your Telegram channel

Telegram connects to Flomixy differently from Instagram, Threads, Facebook, or LinkedIn - there's no login screen to click through. Instead, you connect a bot you control using its token and the ID of the channel or group you want to post to. What you'll need - A Telegram bot token - create one by messaging @BotFather on Telegram and following its /newbot flow. BotFather gives you a token that looks like 123456789:AAH.... - The chat ID of the channel or group you want to post to. Add your new bot as an admin of that channel/group first (it needs posting permission) - you'll need to find the chat ID yourself (for example, by forwarding a message from the channel to a chat-ID lookup bot); Flomixy doesn't detect it automatically. The connect screen walks through these steps and links straight to @BotFather. Connecting your channel 1. Go to Accounts in the sidebar and click Connect account, then choose Telegram. 2. Paste in your bot token and chat ID. 3. Click Connect. Flomixy checks the bot can access that chat - if the token or chat ID is wrong, you'll see an error right in the form (your input isn't cleared, so you can just fix it and try again). Once it succeeds, your Telegram channel appears in the accounts list. Only workspace owners (and above) can connect or disconnect accounts, same as every other network. What you can post Text, images, videos, and albums (multiple images/videos in one post) - the same composer you already use for your other networks. Choose Telegram as one of the target networks on a post like you would Instagram or Facebook. What's different about Telegram - No analytics. Telegram's Bot API doesn't expose view/like/comment counts, so the Analytics dashboard clearly shows "not available" for Telegram posts instead of a blank or loading screen - this isn't a Flomixy limitation, Telegram simply doesn't provide the data. - Deleting a post is best-effort. Flomixy asks Telegram to delete the message, but Telegram doesn't guarantee this always succeeds (for example, if too much time has passed) - if a delete doesn't go through, you may need to remove it manually from the channel. - No reconnect token to expire. Unlike Instagram/Threads/Facebook/LinkedIn, there's no OAuth token that expires - your connection stays valid as long as the bot remains an admin of the channel with posting permission. If posts start failing, check that the bot hasn't been removed or demoted in Telegram itself. Getting a "post published" notification in your Telegram group Once a Telegram channel or group is connected, you can also use it as a notification destination: Flomixy sends a message with a link to every network the post was successfully published to, right after it goes live. 1. Turn on notifications for the channel. Go to Settings → Accounts, find the connected Telegram account, and toggle Notifications on. You need the same permission as connecting or managing social accounts to do this. If your workspace uses brands, the account must be assigned to one first - the toggle stays disabled (with a tooltip explaining why) until you assign a brand from the same card. Workspaces that don't use brands at all can turn the toggle on right away. 2. Opt in per post. In the post composer's Review step, a Telegram notification section appears listing every notification-enabled Telegram channel for the draft's brand (or, in a workspace with no brands, every notification-enabled channel in the workspace). Check the channel(s) you want notified for this post - nothing is checked by default - and optionally write a short custom message that appears above the links. If notification-enabled channels exist but none belong to this draft's brand, the section shows a short note with a link to Accounts instead of disappearing. 3. What the message looks like. If several posts for the same brand are scheduled for the exact same time, they're combined into one message. Links appear in a fixed order (Instagram, Facebook, Threads, LinkedIn, TikTok, Telegram) regardless of which network finished publishing first. A network that failed to publish is simply left out of the message - if every network for a post fails, no message is sent at all. 4. A note on timing. Flomixy waits up to 15 minutes for slower networks (like TikTok) to finish before sending, so the message isn't always instant. A network that finishes after that window (or after the message already went out) gets its own short follow-up "➕ also published" message instead of being missed. Bold and italic in Telegram posts When you write or edit a Telegram post, you can make words bold or italic: 1. Select the words in the caption box. 2. Click B (bold) or I (italic) above the caption. Click again to remove the style. 3. The preview shows the formatting as it will appear in Telegram. Hashtags, @usernames and links can't be styled - the buttons are disabled when your selection touches one. The same buttons are available when you edit a scheduled Telegram post. Message your members directly You can send a private message to the people who follow your channel through your bot. Telegram only lets a bot message someone who has started a chat with it first, so each person needs to do one thing: 1. In Accounts, find your Telegram channel and click Message members. 2. Copy the start link and share it with your members (for example in your channel or group). 3. Each member opens the link and presses Start. They then appear in the list as Active. 4. Write your message and click Send. Flomixy sends it to every active member. If someone blocks the bot or never pressed Start, they show up as Unreachable and the rest of the messages still go out. They return to Active as soon as they press Start again. Good to know: Flomixy can't read your channel's member list (Telegram doesn't share it with bots), so only people who pressed Start can be messaged. Related articles - Getting started: your account and connecting a network - Creating a post with the composer - Understanding your Analytics dashboard

Last updated on Oct 16, 2026

Connecting your LinkedIn profile

Flomixy connects to your personal LinkedIn profile, not a Company Page. Posts you schedule through Flomixy publish under your own name, the same as posting manually from linkedin.com. Requirements - Connect uses your personal LinkedIn profile. LinkedIn Company Pages aren't supported yet (LinkedIn gates Company Page posting behind a separate, manually approved program). - Make sure you're logged into the right LinkedIn account in the browser before you click Connect. LinkedIn doesn't offer an account picker in the connection window. - Only workspace owners (and above) can connect or disconnect accounts. How to connect 1. Go to Accounts in the sidebar. 2. Click Connect account and choose LinkedIn. 3. Sign in to LinkedIn and approve the requested permissions. You'll be sent back to Flomixy with your profile connected. What you can publish - Plain text posts, and posts with one image or one video. - No carousels or multi-image posts. LinkedIn allows only one media item per post. - Video must be MP4, up to 500 MB. - LinkedIn enforces its own text-length limit when the post is published. If a post is too long, LinkedIn rejects it and Flomixy shows it as a failed publish. - Bold and italic: select text in the caption and click B or I in the composer. LinkedIn has no rich text, so Flomixy publishes the styling as special Unicode characters, and the preview shows exactly what will go out. It works on Latin letters (A-Z) and digits only. A selection with other letters (for example Cyrillic or č, š), or a mention or hashtag, can't be styled. Screen readers may read styled text letter by letter, so use it sparingly. Reconnecting LinkedIn access expires roughly every 60 days, and LinkedIn doesn't allow a silent background refresh. When it expires, the account card shows a Reconnect button. Scheduled posts pause until you reconnect (a normal LinkedIn sign-in, same steps as above), then resume automatically. Nothing is lost. Not available yet - LinkedIn analytics. Post and page insights for LinkedIn aren't in the Analytics tab yet. - Company Page publishing. It's on the roadmap. See the Roadmap page in the app for the current status.

Last updated on Oct 02, 2026

Connecting your Facebook Page

Flomixy publishes to a Facebook Page you administer, not a personal profile. Requirements - The Facebook Page must be one you're an admin of; make sure you're logged into that account in the browser before you click Connect. - Only workspace owners (and above) can connect or disconnect accounts. How to connect 1. Go to Accounts in the sidebar. 2. Click Connect account and choose Facebook. You'll be redirected to Facebook to sign in and grant access. 3. Approve the requested permissions - your Page appears in the accounts list. If "Connect with Facebook" doesn't find your Page If it comes back with no Pages even though you are an admin, your Page's Business Portfolio is different from Flomixy's - this is a known Meta limitation while our app is still in review, not a bug. Use "Or share a Page directly" on the Facebook connection card instead: 1. On facebook.com, go to Business Settings, then Accounts, then Pages. 2. Click your Page, then Assign Partner. 3. Paste Flomixy's Business ID (shown in the app when you click "Or share a Page directly"). 4. Grant Content access only - never Full control, Flomixy never needs admin access to your Page. 5. Back in Flomixy, click Sync on the same card and your Page appears as connectable within a few seconds. What you can publish Photos, videos, Reels, carousels and Stories to your Facebook Page. Reconnecting Facebook access is granted through a token that expires periodically. If it becomes invalid, the account card shows a Reconnect button - scheduled posts pause until you reconnect, then resume automatically. Nothing is lost.

Last updated on Sep 02, 2026

OAuth connections vs API keys: which one am I using?

Flomixy has two ways to let another tool act on your account: an OAuth connection and an API key. They do the same kind of job but are created and removed in different places. At a glance | | OAuth connection | API key | |---|---|---| | How you set it up | Click Sign in with Flomixy inside the other app and approve the request | Create it yourself and paste it into the tool | | Where you manage it | Settings → Connected apps | Settings → API keys | | Who can create it | Workspace owner | Workspace owner | | What you see | The app name, the workspace it can use, its permissions and when it was last used | The key name, its scopes, expiry date and last use | | How you stop it | Revoke the app on Connected apps | Revoke the key (then delete it if you want it gone from the list) | | Secret to copy | None, you never handle a secret | The key, shown once | OAuth connections (Connected apps) When you connect an assistant such as Claude on the web by signing in with Flomixy, you approve what it may do and Flomixy remembers that approval as a grant. No key is created and there is nothing to paste or keep safe. Open Settings → Connected apps to see every grant: the app name, the workspace it is limited to (or "All workspaces"), its permissions and when it last used them. Click Revoke to cut it off. The app loses access immediately and has to ask for your approval again to come back. This page lists OAuth connections only. A key you created by hand never shows up here. API keys An API key is a password you create for one tool. Open Settings → API keys → New API key, name it, choose its scopes (the permissions it has) and copy it straight away, because it is shown only once. Paste it into the tool. Give a key only the scopes it needs, and set an expiry date for temporary projects. You can revoke a key at any time and tools using it lose access immediately. See API keys: choosing the right permissions. Which should I use? - The assistant offers Sign in with Flomixy: use the OAuth connection. Nothing to copy, and you can revoke it in one click. - The tool only accepts a key, or you are writing your own script or automation: use an API key. Good to know - Both are created by the workspace owner. Admins and team members should ask the owner. - Posts created through either route wait for human approval by default. The assistant cannot approve or reject posts itself. - Not sure what is connected? Check both pages: Connected apps for OAuth, API keys for keys. Revoke anything you do not recognise. Related articles - Connected apps: see who has access and revoke it

Last updated on Oct 02, 2026

API keys: choosing the right permissions (scopes)

When you create an API key (Settings → API keys → New API key) you choose exactly what the key may do. Each permission is called a scope. Give a key only the scopes its tool needs. Quick tip: start read-only Click Read-only to tick every "read" scope you are allowed to grant, then add write scopes one by one. Clear unticks everything. What each scope allows | Group | Scope | What it allows | |---|---|---| | Posts | POSTS_READ | View posts, drafts and hashtag sets. | | Posts | POSTS_WRITE | Create, edit and delete posts. | | Accounts | ACCOUNTS_READ | List connected accounts, brands and what each channel supports. | | Accounts | INSTAGRAM_ACCOUNTS_READ | List connected Instagram accounts. | | Media | MEDIA_READ | Browse the media library and stock photos. | | Media | MEDIA_WRITE | Upload files to the media library. | | Schedule | SCHEDULE_READ | Read the best times to post and the next free slot. Owner only. | | Analytics | ANALYTICS_READ | Read account and post performance numbers. Owner only. | | Webhooks | WEBHOOKS_WRITE | Create, list and delete webhook subscriptions that send workspace events to a URL. Owner only. | | Approval | POSTS_AUTO_APPROVE | Let posts created with the key skip human approval when the request asks for it. The agent publishes without human review. Owner only. | Why some scopes are greyed out Scopes marked Owner only can be granted by a workspace owner only. If you are an admin they appear greyed out with the note "Only a workspace owner can grant this". Ask your workspace owner to create the key. Approval: on by default, and who reviews Every post an API key or an AI agent (MCP) creates waits for human approval by default. Nothing is published until someone approves it. When creating a post, the create_post tool (and POST /public/posts) accepts an optional approval object: { "approval": { "mode": "required", "approverId": "<member id>", "message": "Please check the discount wording" } } - mode: "required" (default) or "none". - approverId: send the post to one specific team member for review (they alone get the review notification and email). Use the new list_approvers tool to see who can approve (id and name only). A member outside your workspace, or without the right to approve, is rejected with a 400 and no post is created. - approverEmail: an external reviewer (for example a client) who receives a review link by email, as in the Composer. - message: a note shown to the reviewer. Any key may choose a reviewer. Only a key with the owner-granted POSTS_AUTO_APPROVE scope may use "mode": "none" to publish without approval; any other key gets a 403 and nothing is created. A brand set to owner requires approval (and the client approval flow) still forces approval even with "none". An agent can never approve or reject posts itself. Risk: prompt injection. An AI agent that reads untrusted content (web pages, emails, comments) can be tricked into acting on instructions hidden in it. With POSTS_AUTO_APPROVE such an agent can publish to your accounts with no human check. Grant the scope only to keys whose agent never handles untrusted input, and prefer the default (approval required) otherwise. Every post published this way records which API key created it. Good to know - The key is shown once, right after you create it. Copy it immediately. - Revoke a key at any time from the API keys page; tools using it lose access immediately. - A revoked or expired key stays in the list until you delete it (key menu → Delete). Deleting is permanent; an active key must be revoked first. Posts created with a deleted key keep working and show "scheduled via a deleted API key". - Set an expiry date for keys used in temporary projects.

Last updated on Oct 02, 2026

Connect an AI assistant to Flomixy

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.

Last updated on Oct 02, 2026

Connect ChatGPT, Gemini, Cursor and n8n to Flomixy

Flomixy's connection address is the same for every assistant: https://mcp.flomixy.com/mcp. What differs is how each assistant signs in: some can sign in with your Flomixy login (OAuth), some only accept an API key. Which assistant, which sign-in | Assistant | API key | Sign in with OAuth | |---|---|---| | Claude (web) | Yes | Yes | | Claude Code | Yes | No | | ChatGPT | No | Yes (only option) | | Gemini CLI | Yes | No | | Gemini (web app) | No | Yes (only option) | | Cursor | Yes | No | | n8n | Yes | No | If you are not sure, use OAuth where it is offered: there is nothing to copy and nothing to leak. Sign in with OAuth (Claude web, ChatGPT) Only the workspace owner can connect an assistant this way. If you are not the owner, the consent screen tells you so; ask the owner to approve the request. 1. In the assistant, add a custom connector (in ChatGPT: a custom app, see the ChatGPT steps below) with the address https://mcp.flomixy.com/mcp. Leave any API key field empty. 2. Start the sign-in from the connector (the wording may differ slightly). 3. Sign in to Flomixy if you are not already. 4. Pick the workspace you want to connect. 5. Review the permissions on the Authorize access screen, then click Allow. Click Deny to cancel. You are sent back to the assistant, which can now work with that workspace. Every post it creates still waits for human approval by default. ChatGPT ChatGPT connects only with OAuth. An API key does not work here, so do not spend time pasting one. Use chatgpt.com in a browser; the desktop app may not offer custom connectors. Menu names below are as shown in the English interface (verified live, October 2026). 1. Open Settings → Security and turn on Developer mode (named "Developer mode" in English, "Programerski režim" in Serbian). It is only available on some plans. 2. Open Apps (the sidebar entry, in Settings it is "Apps"), click the + at the top right, and choose New app. 3. Fill in Name (for example "Flomixy"), leave Description empty, set the connection to Server URL with https://mcp.flomixy.com/mcp, and set Authentication to OAuth. 4. Tick I understand and want to continue, then click Create. 5. Open the new app, click the ... menu → Manage, then Connect another account and Sign in with your Flomixy account. 6. A Flomixy page asks you to Authorize access. Pick the workspace and click Allow. Only the workspace owner or a platform super admin sees Allow. 7. Start a new chat, make sure Flomixy is attached in the message box, and ask for something harmless such as "Show my last 5 Flomixy posts". What ChatGPT is allowed to do After you click Allow, ChatGPT can read and create posts, list your connected accounts and brands, read and upload media, read the posting schedule and best times, and read analytics. The schedule and analytics permissions are only offered when the workspace owner signs in. Every post ChatGPT creates waits for a person to approve it. ChatGPT cannot be given the skip-approval permission: it is not available through sign-in, so nothing it creates is published on its own. If you connected ChatGPT before October 2026, disconnect it and connect it again to get these permissions. If you see a 401 or 500 error while signing in, see Troubleshooting your AI assistant connection. Gemini - Gemini CLI connects with an API key. Add this to your settings.json (usually ~/.gemini/settings.json), with your own key in place of YOUR_API_KEY: { "mcpServers": { "flomixy": { "httpUrl": "https://mcp.flomixy.com/mcp", "headers": { "x-api-key": "YOUR_API_KEY" } } } } Restart the CLI and run /mcp to check that flomixy is listed as connected. Create the key as described in Connect an AI assistant to Flomixy. - The Gemini web app connects with OAuth (no API key). It is available to personal Google accounts only, aged 18 or over and in the US, with Keep Activity turned on; work and school accounts are not supported. 1. On gemini.google.com open Settings → Connected Apps (if you do not see it, click Personal Intelligence first). 2. Under Custom apps enter https://mcp.flomixy.com/mcp and click Next, then Connect and Agree and continue. 3. On the Flomixy Authorize access page pick the workspace you want Gemini to use and click Allow (workspace owner or platform super admin only). Check the workspace name before you click Allow. 4. In a new chat type @ and pick the Flomixy app, then ask for your accounts or a draft post. Gemini asks you to allow each tool call. Every post Gemini creates waits for human approval, same as with ChatGPT. Cursor and n8n Both use an API key. Create a key first (Settings → API keys), starting with read-only scopes. Cursor: add the server in Cursor's MCP settings, or edit ~/.cursor/mcp.json directly: { "mcpServers": { "flomixy": { "url": "https://mcp.flomixy.com/mcp", "headers": { "x-api-key": "YOUR_API_KEY" } } } } n8n: add an MCP Client Tool node to your AI agent and set: - Endpoint: https://mcp.flomixy.com/mcp - Server Transport: HTTP Streamable (not the deprecated SSE option) - Authentication: Header Auth, with the header name x-api-key and your API key as the value Store the key in n8n credentials, never directly in a workflow you share or export. Disconnect - Assistants connected with OAuth: open Connected apps in your Flomixy settings, find the app, click Revoke, then confirm Revoke access?. The app loses access immediately and you can connect it again later. - Assistants connected with an API key: open Settings → API keys and revoke the key. Every tool using that key stops working at once. Troubleshooting - I see a 401 or 500 error while signing in with ChatGPT. The cause is on Flomixy's side, not in ChatGPT or your settings, so recreating the app will not help. Contact Flomixy support with the time of the attempt and the workspace name. - ChatGPT says authentication failed. Make sure you chose OAuth and left the API key empty; ChatGPT cannot use a key. - The consent screen says only the owner can connect. Ask the workspace owner to do the sign-in. - "This authorization link is invalid or has expired." Start the connection again from the assistant. - "Unauthorized" with an API key. The key was copied wrong, revoked, or lacks the scope for that action. Create a new key. - The assistant cannot see the tools. Check that the connector is switched on in the chat, or that /mcp shows it connected.

Last updated on Oct 08, 2026