Connect ChatGPT to Profinity
Connect ChatGPT to Profinity with a Custom GPT built from the AI Skills pack, so that ChatGPT can read your instance and save dashboards, rules, and collections to it. The Custom GPT calls the Profinity REST API, which every edition includes, so it does not need the AI licensed feature. ChatGPT cannot use the Profinity MCP Server, because it connects only to public servers that use a different sign-in from Profinity's token.
ChatGPT runs on the internet, so it cannot open localhost or trust a certificate that you accepted on your computer.
Before you start, you need:
- A public HTTPS address for Profinity, with a certificate from a trusted authority. Refer to HTTPS certificates.
- A service account token with the permissions for the data the GPT reads and for anything it saves. A service account needs Users & Groups, which needs a Server licence. Refer to Service accounts and Roles and permissions.
profinity-ai-skills.zipfor your Profinity release, from Prohelion.
A Custom GPT has no shell on your computer. The dashboard, rules, collections, derived tag, and app skills read and save through the REST API, and the script and plugin skills give you commands to run yourself. Refer to What each tool can do.
Set up ChatGPT
- In ChatGPT, create a Custom GPT.
- Paste the instructions from the pack, upload the example files, and import the OpenAPI actions file.
Before you import it, open the file and find the address in the
serversentry, which readshttps://REPLACE-WITH-YOUR-PROFINITY-HOST. Replace the whole address with your public HTTPS address for Profinity. The file list and the order of those three actions are in Set up ChatGPT. - Set the action authentication to an API key of type Bearer, and paste the service account token. Do not choose OAuth.
- Save the Custom GPT.
- Start a new chat with that GPT, and ask: "What components are in my active profile?"
A list of component names confirms that ChatGPT can reach the REST API and that Profinity accepts the token. The GPT shows you what it is about to save, and asks before it saves a change. For the token header, refer to Authenticate to the Profinity REST API.
Fix a failed connection
| What you see | Cause | What to do |
|---|---|---|
| The action cannot reach the host | ChatGPT is not on your private network | Use a public HTTPS address, and allow it through the firewall |
| The action reports a certificate error | The certificate is self-signed, or does not name the public host | Select a certificate from a trusted authority on the Web tab. Trusting the generated certificate on your computer has no effect on ChatGPT |
| The action returns 401 | The token is incomplete, or Generate Token has replaced it | Paste the current token into the action authentication |
| The action returns 403 | The account lacks the permission for that call | Add the permission to one of the account's roles |
| The script or plugin skill stops after printing commands | A Custom GPT cannot run commands | Run the commands on a computer where the Profinity tools are installed, or use Claude Code, Codex, or Cursor |
When the Custom GPT can read the instance, ask it for the dashboard, rule, or collection you want to build. Refer to AI Skills.