What Connectors Exist

There are plenty of ready-made connectors. A connector itself does nothing: it links the chat to a system, passes requests in, and brings answers back.

What to ask for is the chat's decision. What is allowed in that system at all is set by the connector. Through some of them the chat only searches and reads; through others it creates records and sends messages on your behalf.

What gets connected is what the company uses every day: mail, calendar, file storage, a knowledge base, work systems.

What the chat does in a connected system

Here is what the chat does in systems that already have ready-made connectors. The set of actions differs by service and changes over time.

  • In Gmail the chat searches and reads messages, prepares drafts, sends and forwards them.
  • In Google Calendar the chat shows events, creates, moves, and deletes meetings, and finds a time when everyone is free.
  • In Google Drive the chat finds and reads Google Docs and Google Sheets and saves files created in the conversation to the same place.
  • In Microsoft 365 the chat finds and reads files in SharePoint and OneDrive, messages in Outlook, and messages in Teams.
  • In Slack the chat sends messages and finds information in the history.
  • In QuickBooks the chat creates, edits, and sends invoices to clients and answers questions about payroll already paid.
  • In GitHub the chat searches code in repositories and explains it.

Beyond these, companies connect sales, support, task tracking, and HR systems: Salesforce, ServiceNow, Jira, Workday, SAP. Microsoft counts more than 100 ready-made connectors for its own Copilot.

Your company has its own set of applications. Ask your administrator which of them you can connect to.