Profiles, packs and REST APIs
What ChatPilot knows about a kind of system or one product, how to add a pack, and connecting a system that has a REST API but no MCP.
Profiles
A profile says what ChatPilot knows about a kind of system or one product: what an account is there, which tool gives which figure, and the client card, alerts, reports and example questions that go with it. Profiles are data only: no code and no keys.
ChatPilot comes with a general profile for each kind of system (CRM, ad platform, shop, helpdesk, finance, projects & tasks, calendar). A system gets:
- the profile you picked under What ChatPilot understood → Correct → Profile, else
- the product profile that fits it best, else
- the general one of its kind.
Your corrections always win over the profile, and the profile wins over ChatPilot's own reading. Alerts in a profile start off, and its reports are drafts.
Settings → Connected systems → Profiles lists the product profiles and packs ChatPilot found, and any file it couldn't use, with the reason.
Packs
A product's own profiles come as a pack: a folder or a git repository. Install one in a terminal:
chatpilot profiles install <folder or git URL>
Packs go into the packs folder in ChatPilot's settings folder; your own profiles go into its profiles folder. chatpilot profiles lists what was found. A connected system can also offer its own profile; ChatPilot checks it like a pack's and uses it for that system only, unless a pack or your own profile fits it.
Systems with a REST API (no MCP)
Many tools have an ordinary REST API but no MCP server. A pack can describe such an API, read only, and ChatPilot runs it like any other system. Everflow, Affise and Scaleo come with ChatPilot this way: you give the address and an API key, ChatPilot tries the key once, and only then adds the system.
A tool that isn't shipped yet can get its own pack. The format, with a made-up example, is in ChatPilot's repository under docs/profiles/ (rest-api.md for REST APIs).
Checked against ChatPilot 0.1.0b1. Report a problem with this page