AI assistant API: funnels, internal links and ChatGPT in the browser

An AI assistant connected to Content Review can do three more things on your site, through the same safe sign-in it uses to hand in proposals: work with the funnels of Journey analytics, run the Internal links tool and, for ChatGPT, connect in the browser. The connection is the REST address of Content Review, baza-helper-content-review/v1.

Funnels of Journey analytics (Pro)

A funnel is the path you expect a lead to take, step by step, ending in a goal. This needs Baza Helper Pro with Journey analytics; without it the funnel routes answer 404. The assistant can:

  • read your funnels with their numbers for a period: how many leads reached each step, where most left and how many met the goal;
  • look at your site first with GET /funnels/site-scan: the contact, pricing and booking pages, the buy buttons, the forms and the pages and buttons visitors really used, so a funnel is built from real values;
  • create, change and delete funnels, up to 10 funnels of up to 12 steps.

Funnel changes by the assistant are applied at once, like pressing Save funnels yourself. The earlier value is written to a log that you can read at /assistant-log, with who made the change and what it was before. A deleted funnel can be made again from the log. Ask it to analyse first: which step of my funnels loses the most leads, and what would you change? Then decide what it may change.

Instead of editing links inside your articles, the assistant uses the Internal links tool itself. It runs the scan, reads suggestions, links, rules and settings, accepts or rejects suggestions, adds and changes rules for the words to link, and removes or restores links. The links are still added while the page is built; the article text is never rewritten.

  • Suggestions, links, the scan, accepting and rejecting need a user who can edit other people’s posts, for example an editor.
  • Rules and settings need an administrator. Another user gets a clear 403 message.

ChatGPT connector (without a Custom GPT)

ChatGPT on the web can connect to an MCP server that takes no key, and Baza Helper makes such a connector for you. This is the easier way. The connector does not include Search Insights, which keeps its own sign-in. The Custom GPT below is now a fallback, because OpenAI plans to close Custom GPTs on 11 December 2026.

  1. Open Content Review, Setup, and make a connector: choose the assistant user (Assistants tab) and the tools: content, funnels and internal links.
  2. Copy the secret address. It is shown once and kept only as a hash. If you lose it, revoke it and make a new one.
  3. In ChatGPT open Settings, Connectors, turn on Developer mode (Advanced) and create a connector: a name, the address as the URL of the MCP server, and No authentication.
  4. In a chat, turn the connector on and ask: List my funnels.

Keep it safe

  • The address is a secret. Never paste it into a chat.
  • Whoever knows the address can do what that user may do with the chosen tools, and no more.
  • Press Revoke when you finish: the connector stops at once.
  • It works only on a site with https, with up to 10 connectors and 120 requests a minute. Blocking the user stops the connector.
  • Who has Developer mode and how ChatGPT names its settings changes over time, and we did not try these steps in a real ChatGPT account.

ChatGPT with a Custom GPT (a fallback)

ChatGPT in the browser cannot run commands on your computer, so it connects through a Custom GPT with an action. Open Content Review, Setup, the card ChatGPT in the browser (a Custom GPT):

  1. Make a separate user and an Application Password on the Assistants tab.
  2. Press Make the key. The key is made from the user name and the password in your browser, and nothing is sent.
  3. Copy the schema for what ChatGPT should do: content proposals, funnels, internal links or Search Insights. The schema is an OpenAPI 3.1 file with your site address, also served at GET /openapi?api=content|funnels|internal-links|search.
  4. In ChatGPT, open Explore GPTs, Create, Configure, add an action and paste the schema.
  5. Under Authentication choose API Key, Auth Type Custom, the header name X-Content-Review-Auth, and paste the key. For the Search Insights schema choose Bearer and a token from its tab.
  6. Test it in the preview with a request such as “List my funnels”, then press Update.

What the answers mean

  • 401: the key is wrong or missing. Make the key again from the user name and the Application Password.
  • 403: the user may not do this. Rules and settings of Internal links need an administrator.
  • 404: the tool is not available, for example the funnels without Journey analytics, or the address is wrong.
  • Could not connect: ChatGPT cannot reach the site. It must be public and on https, not on localhost or behind a login.

Good to know

  • OpenAI plans to retire Custom GPTs on 11 December 2026 and says custom actions are not moved to its new plugins.
  • ChatGPT connectors on the web take no key, so the connector above uses a secret address. Baza Helper does not offer OAuth.
  • Claude Code, Codex, Gemini CLI and Cursor connect as before and are not affected by this.
  • We have not tried these steps in a real ChatGPT account, so treat them as a guide and check each screen.

When you are done, block or delete the assistant’s user on the Assistants tab.

Last Modified: 07.11.2026