Connections

A connection is a link between TrailKit and one of the tools you already use. Gmail, Slack, Notion, Google Drive, Salesforce, HubSpot, your calendar, your CRM, your accounting system, and about a thousand others. Once a tool's connected, agents can read from it, write to it, and react to things that happen in it, on your behalf, without you having to copy-paste between tabs.

Adding one

Open Integrations. It's the puzzle-piece icon in the chat composer, or there's an item for it in the sidebar. Search for the product, click Connect, and sign in. You'll go through the vendor's normal login, grant permission, and bounce back. Usually under a minute.

We never see your password. The connection only grants the specific permissions you click "approve" on. You can pull it back anytime from the same panel.

More than one of the same tool

Connect as many as you need. Two Gmails (work and personal), three Drives, a personal Slack and a team Slack, a handful of Stripe accounts across different entities. Agents pick the right account when it's obvious from context and ask you which one to use when it isn't.

What agents can actually do once a tool's connected

Whatever you can do with that login, basically. Some examples to make it concrete:

• Gmail / Outlook. Read messages, search, draft replies, send mail, manage labels.
• Slack / Teams. Read channels and DMs, post, react, start threads, look people up.
• Calendar. See your schedule, propose times, book and move meetings, decline conflicts.
• Drive / Dropbox / OneDrive. Find files, read them, make new ones, share them with the right people.
• CRM (Salesforce, HubSpot, Pipedrive). Look up accounts and contacts, log activity, create and update deals.
• Project tools (Notion, Linear, Jira, Asana). Find tickets, update status, comment, create new work.

Not sure if something's possible? Just ask the agent. It knows what each connection can do and will tell you up front if your request isn't supported.

Pulling a connection

In Integrations, find the connection and hit Disconnect. Any agents that were using it pause cleanly. They don't crash silently. They tell you they've lost access and wait for you to either reconnect or change the plan. We delete the stored credentials on disconnect.

When a connection breaks

It happens. The vendor signs you out, an IT policy changes, a password rotates. The agent will tell you the connection needs a refresh, and the Integrations panel will mark it with a Reconnect button. Click it, sign in again, you're back.