TL;DR, Quick Answer
9 min readInstall the Flowsery plugin from its listing in ChatGPT, sign in to Flowsery in the window that opens, and never paste a token into the dot chat. OpenAI's dots docs say a dot can use supported plugins installed and enabled for your account, so prove it with one read call. 23 of the plugin's 28 tools only read, and only a Flowsery Admin or Editor can connect it, so ChatGPT's own approval setting is what holds back the five writes.
Connecting an OpenAI dots plugin for web analytics takes one install, one sign-in and one read-only test, and the test is the step that matters. OpenAI launched dots at DevDay on 29 September 2026: an always-on ChatGPT agent, powered by GPT-6 Astra, with its own cloud computer and browser. As of October 2026, Flowsery is listed in ChatGPT's plugin directory, so the way in is the Flowsery plugin listing and its "Install plugin" button.

The short version: open the Flowsery plugin in ChatGPT, click "Install plugin", sign in to Flowsery when its window opens, then ask your dot to list your Flowsery websites before you ask it anything that matters.
What is an OpenAI dots plugin?
An OpenAI dots plugin is a service connection your dot can call, and OpenAI's plugin docs define a plugin as MCP servers plus skills in one directory shared by ChatGPT and Codex. OpenAI's dots docs say a dot "can use supported plugins installed and enabled for your account". The Flowsery plugin is in that directory and runs on Flowsery's hosted MCP server at https://mcp.flowsery.com/mcp, so installing it from the listing is the whole connection.
Can a dot use the Flowsery plugin?
A directory plugin you installed and enabled is what OpenAI's dots docs describe when they say "supported plugins", and the Flowsery plugin is one. OpenAI publishes no list of the plugins a dot supports, though, so a plugin that answers in a regular chat is not yet proof that your dot calls it.
So treat the first conversation as an experiment. Ask the dot to list your Flowsery websites and show the raw response. Website IDs and domains mean the dot is calling the plugin. A tidy explanation of how Flowsery works means the dot browsed instead, and nothing further in this guide applies until that changes.

How do you add Flowsery to ChatGPT for a dot?
Flowsery goes into ChatGPT as a listed plugin in four steps, all on a desktop app or desktop browser, because OpenAI says you cannot create a dot on mobile or mobile web. The ChatGPT analytics plugin guide covers the same install for regular chats.
Use the Flowsery plugin only. Do not open flowsery.com in your browser.
1. List the Flowsery workspaces and websites you can reach. Show the raw
website IDs and domains.
2. For the first website, get last week's overview against the week before,
timezone Europe/Berlin. Show visitors, sessions, bounce rate and revenue
for both weeks.
3. Do not create, update or delete anything in Flowsery. If a step needs a
write, stop and ask me.
Where does the Flowsery credential go?
The Flowsery credential goes into Flowsery's own sign-in window, never into a message to your dot. OpenAI's safety post says a secret "placed separately in a readable message or document may still be visible to the model", and its safety FAQ says password protections don't cover passwords shared in a chat or through a plugin. Flowsery's MCP server signs you in with OAuth, so the secret never enters the conversation. The server also takes a Bearer header for clients without OAuth, and a dot chat has no header field.
Signing in with OAuth has two consequences. Flowsery's API reference says an OAuth sign-in "can reach every workspace its member belongs to, across organizations", and a call that names no workspace lands in your default one, so an agency has to name the client workspace in every task. And your Flowsery role decides whether the dot connects at all: every Flowsery sign-in needs the flowsery.write permission, which only Admins and Editors hold, so a Viewer or Contributor gets permission_denied at sign-in and on every call. A Viewer role cannot turn a dot into a read-only one.
Which Flowsery calls are safe reads, and which write?
Flowsery's public API documents 28 operations as of 29 September 2026, and 23 of them only read. The other five change data.
| Call | What it returns | Changes data |
|---|---|---|
GET /overview, /timeseries, /breakdown | Headline metrics, trends, any dimension | No |
GET /pages, /referrers, /channels, /campaigns and the other breakdowns | Where visitors came from and landed | No |
GET /goals, /realtime, /realtime/map | Completions, and who is on the site now | No |
GET /issues, /issues/{issueId}, /visitors/{visitorId} | AI-detected issues, one visitor's timeline | No |
GET /websites, /workspaces, /metadata | What this sign-in can reach | No |
PATCH /issues/{issueId} | Moves an issue between statuses | Yes |
POST /goals, DELETE /goals | Records or deletes goal completions | Yes |
POST /payments, DELETE /payments | Records or deletes payments | Yes |
The plugin carries all five writes. Flowsery's hosted MCP server has 28 tools: 23 reads and five writes, which update an issue's status, record and delete goal completions, and record and delete payments. The payment tools change analytics records only and never charge or refund anyone. update_issue_status, the plugin's version of PATCH /issues/{issueId}, is the easy one to overlook: a suspended issue disappears from the default list, so a dot tidying the backlog shortens the list without fixing anything on it.
OpenAI says a dot always confirms before "permanently deleting data", which on paper covers delete_goals and delete_payments. It does not reach track_payment, which deletes nothing but adds revenue to your reports. ChatGPT's approval setting, below, is the check that does not depend on how the dot classifies a call. Teams that want writes impossible at the server can deploy Flowsery's read-only worker from github.com/Flowsery/remote-mcp, where every tool is a GET, and add it to ChatGPT by hand in place of the listed plugin.
How do you keep a dot's writes in check?
ChatGPT's own approval setting keeps a dot's writes in check, because a Flowsery role cannot: only an Admin or Editor can connect the plugin, and both roles hold the five writes. The gate is Custom Rules, OpenAI's four settings: take action without asking, take action when you say so or if pre-approved, ask before taking action, and hand off to you. Start on "Ask before taking action", and loosen it only after a month of reads has earned more.
Flowsery
Start Your 14-Day Free Trial
Real-time dashboard
Goal tracking
Cookie-free tracking
Does a dot's own browsing show up in Flowsery?
A dot visits your site in a real Chrome browser on a Linux machine that OpenAI maintains, and whether Flowsery counts that visit turns on one flag OpenAI has not documented. Flowsery's tracking script at cdn.flowsery.com/main.js skips any browser that reports navigator.webdriver as true, and session recording skips it too. OpenAI's dots documentation, checked 29 September 2026, names no user agent string, no IP range and no robots.txt token for a dot, and says nothing about that flag.
That leaves two outcomes for a dot that opens your pricing page. If its Chrome sets the flag, Flowsery drops the visit. If it does not, the visit counts as an ordinary Chrome session with nothing marking it as an agent, the same way Meta Muse visits land as human ones.
- Each dot has its own cloud computer and browser
- OpenAI maintains the Linux system and the Chrome browser
- Flowsery's tracker ignores
navigator.webdriver === true
- A user agent string for dots
- An IP range for dot computers
- A robots.txt token
- Whether a dot's Chrome sets
navigator.webdriver
Test it once. Ask the dot to open a URL nobody else uses, such as /pricing?src=dot-test, then check Flowsery's realtime view. GET /realtime/map lists visitors from the last five minutes with browser, operating system and current URL, so a counted dot visit shows up under that URL. Plugin calls never touch the site: an API overview loads no page and fires no tracker. Bot traffic filtering covers the wider problem.
What does an analytics dot cost?
Your first dot is included in ChatGPT Pro ($100, $200 or $500 a month) or Business Premium at no extra cost, according to OpenAI's launch post. Flowsery includes its API on both plans: Team at $250 a month and Pro at $500, each with a 14-day free trial and no card. Geography is the real gate. Dots on ChatGPT Pro exclude the EEA, the UK and Switzerland and Business Premium covers all supported ChatGPT regions.
Where do reporting and session analysis go from here?
The OpenAI dots plugin for analytics reporting puts the Monday numbers on a recurring task and covers the approval a dot wants before it posts into Slack. The OpenAI dots plugin for session analysis points the dot at Flowsery's AI-detected issues. Other agents get the same setup in the Meta Muse connector guide and the Grok bot template guide, and the dot reads the same numbers as Flowsery's web analytics dashboard. The ChatGPT analytics plugin guide covers the same plugin in regular chats.
Frequently Asked Questions
Is Flowsery in the ChatGPT plugin directory?
Yes. As of October 2026, the Flowsery plugin is listed as "Flowsery, By Taras Shynkarenko, Website traffic and issues". Click "Install plugin" and sign in to Flowsery in the window that opens. There is no URL to paste.
Can I paste a Flowsery API token into my dot instead?
No. OpenAI says a secret in a readable message can be visible to the model. Flowsery's MCP server signs you in with OAuth, so no token crosses the conversation. Delete any token that lands in a chat at flowsery.com/api-tokens.
Why does the dot describe Flowsery instead of reading my data?
The dot browsed the web instead of calling the plugin. Confirm the plugin is enabled in ChatGPT's Plugins tab, tell the dot "use the Flowsery plugin, not the browser", and ask for raw website IDs.
Can the dot change my Flowsery data?
Only through five of the plugin's 28 tools: update_issue_status, track_goal, delete_goals, track_payment and delete_payments. A Flowsery role cannot block them, because only Admins and Editors can connect the plugin. Set Custom Rules to "Ask before taking action" so each write waits for your yes. The payment tools change analytics records only and never charge or refund anyone.
Why are the numbers from the wrong client?
An OAuth sign-in reaches every workspace your Flowsery account belongs to, and a call that names none lands in the default workspace. Name the workspace at the top of each task.
How do I remove the dot's access to Flowsery?
Remove the Flowsery plugin in ChatGPT's Plugins tab. Moving the account it signed in with below Editor also cuts it off, because Flowsery refuses every call from a Viewer or Contributor. OpenAI says you cannot view or edit a dot's memories, and deleting the dot is the only way to clear them, so numbers it already learned stay with it.
Can a ChatGPT Pro dot read my Flowsery data?
Yes, where dots on Pro are available. 23 of the plugin's 28 tools only read, which covers every report, breakdown and issue list. Ask the dot to list your Flowsery websites first, to prove it calls the plugin. Dots on ChatGPT Pro are not available in the EEA, the UK or Switzerland.
Do I need a paid Flowsery plan to connect the plugin?
Flowsery includes its API on both plans, Team at $250 a month and Pro at $500. Each comes with a 14-day free trial and no card.
Can I set up a dot on my phone?
OpenAI says you cannot create a dot on mobile or mobile web. Do the setup on the desktop app or a desktop browser, starting with the Flowsery plugin listing.
Will a dot's visit to my site count in Flowsery?
Flowsery's tracker skips any browser that reports navigator.webdriver as true, and OpenAI has not documented whether a dot's Chrome sets it. Open a URL nobody else uses, such as /pricing?src=dot-test, and check the realtime view. Plugin calls never load a page, so they never count as visits.
Flowsery
Start Your 14-Day Free Trial
Real-time dashboard
Goal tracking
Cookie-free tracking
Start a Flowsery trial and install the plugin, or read the API reference first.
Sources: Introducing dots, How we build safety, security and privacy into dots, OpenAI help on getting started and safety, the dots user docs, ChatGPT plugins, the Flowsery API reference and the Flowsery OpenAPI spec. Checked 29 September 2026; the Flowsery plugin listing checked October 2026.
Was This Article Helpful?
Let us know what you think!
See us more often in Google
One click marks Flowsery as a preferred source, so our articles sit higher in your Top Stories, AI Mode, and AI Overviews.
Before you go...
Flowsery
Revenue-first analytics for your website
Track every visitor, source, and conversion in real time. Simple, powerful, and cookie-free.
Real-time dashboard
Goal tracking
Cookie-free tracking
Related Articles


Ask Your Traffic Questions Through a Manus Cue Connector for Web Analytics
Build a Manus Cue connector for web analytics on the Flowsery MCP server: where Manus takes the URL and token, what Cue leaves out, and which calls write.


Schedule the Monday Report With an OpenAI dots Plugin for Analytics Reporting
Run a weekly report with an OpenAI dots plugin for analytics reporting: six Flowsery reads on a recurring task, and the Slack post that needs a rule.


Rank Broken Sessions With an OpenAI dots Plugin for Session Analysis
Point an OpenAI dots plugin for session analysis at Flowsery issues: three reads rank what broke, and PATCH /issues is the one write to keep out of reach.

