ChatPilot
Connected systems

Connect a system

Add a CRM, helpdesk, admin panel or other tool under Settings → Connected systems, so ChatPilot can look things up there.

A connected system is a tool your work runs on: a CRM, a helpdesk, a shop, an ad platform, a tracker, a calendar, your own back office. Once it's connected, ChatPilot can look things up there while you discuss a chat, write a draft or show a client's figures next to their chat.

Reading is all ChatPilot does by itself. Anything that changes something in the system is an action: off until you switch it on, and even then it only runs when you press Run (Actions in connected systems).

Settings → Connected systems: a system with what ChatPilot can look up and its actions
Settings → Connected systems: a system with what ChatPilot can look up and its actions

Add a system

  1. Open Settings → Connected systems and click ＋ Add system. The list opens right under the card's title; Cancel there closes it without adding anything.
  2. Pick a system from the list. Each tile says how you connect: sign in, token or API key. Systems that fit what you use ChatPilot for come first, under Suggested for what you use ChatPilot for. Not in the list? Pick Other (any MCP server) (Any other system (MCP)) or one of the webhooks (Zapier, Make, n8n and webhooks).
  3. Fill in the form. It shows the system's own notes and a link to its documentation. Give it a Name, how the system is called in ChatPilot, e.g. "CRM" or "Shop".
  4. Choose Read it (see below).
  5. Click Connect (or Sign in with …). ChatPilot tells you how many of the system's tools only read, then looks at what it can do there.

What the form asks depends on the system:

  • A system on your own domain asks for your address and shows Connects to … with the full address it will use.
  • A sign in system opens its own sign-in page in a new tab. ChatPilot gets a token, never your password, and keeps it fresh by itself.
  • A token or API key system asks for the key. Use a read-only key where the system offers one.

Read it has two choices:

  • only in chats I bind it to (safest for client data): ChatPilot reads it only in chats you bind to it, and only for the account that chat is about (Live data in a chat).
  • in every discussion with ChatPilot: for systems that aren't about clients, such as your own project tracker.

Keys, tokens and webhook addresses go into your computer's secret store (the Keychain on a Mac), never into a file.

What you see for each system

  • A label with its state: reads: N tools, signed out, no key or can't reach it, and whether it is read in all discussions or in N chats bound.
  • What ChatPilot can look up here: a short summary in plain words, example questions and what an account is there.
  • What ChatPilot understood: the kind of system and which tool gives which figure (What ChatPilot understood).
  • Monitors: checks that alert you (Monitors and stop-loss).
  • Actions — ChatPilot runs one only when you press Run: everything that changes something, each with its risk (creates, changes, sends, deletes, money, budget). When ChatPilot finds actions that only create something new, it offers Allow creating things; the rest you switch on one by one.

Buttons

  • Learn what it can do / Learn again: ChatPilot reads the system's tools again and updates what it can look up and which actions there are.
  • Sign in again: shown when a sign-in ran out or the system revoked it.
  • Remove: deletes the key (or revokes the sign-in) and unbinds the system from every chat. The actions log stays.

When a system changes

Every hour ChatPilot checks whether a system's tools changed. If so, it learns the system again by itself and tells you once, on the system's card and in Telegram. Your corrections and switches stay; new actions arrive off, and actions whose tool is gone are switched off and listed as no longer offered.

Tickets in a GitHub repository

＋ GitHub repository sends tickets to a repository of your choice: see GitHub.

The systems in the list

Checked against ChatPilot 0.1.0b1. Report a problem with this page