In short
A link between an agent and a real system: email, calendar, files, the CRM, the site. Connecting your people to their systems is one of the first things we do in month one.
A connector is what lets an agent act in the world instead of talking about it. With an email connector it reads and drafts. With a calendar connector it schedules. With a file connector it reads the shared drive. With a site connector it publishes.
Getting a team's connectors set up is a larger unlock than it sounds. Most people have never had an assistant that could see their calendar, their inbox, and their documents at once. Once the connectors exist, every prototype after that is faster to build, because the agent already has hands.
Connectors are scoped by trust boundaries. Read here, write there, never that.
Example
What it looks like.
Week one connectors for an operations lead: Gmail (read, draft), Google Calendar (read, propose), Drive (read), the CRM (read, update), the chat app (send).Related
Read next.
- agentSoftware that reads its instructions, looks at the situation, takes actions with real tools, and reports back. Runs on a schedule or on a trigger, without being prompted.Read the definition
- trust boundaryThe written line between what an agent may touch and what it never does. Set before anything runs. Autonomy and safety move together.Read the definition
- Ninety-day transformationA fixed three months, in and out. Build in month one, live by day 30. Adopt in month two. Own in month three, when we hand over the keys, the instructions and the files.Read the definition
- MCPA standard way to give an agent a tool. An MCP server exposes something (image generation, a database, a search API) that any agent can call the same way.Read the definition