3 min lesson
Workspace connectors: the apps the whole account can use
How workspace connectors differ from Max connectors. Shared MCP tools, scopes, and workflow triggers.
A workspace connector is an account-level connection. It lives under Integrations → Workspace connectors. Agents, workflows, and Studio use it. Max connectors do not.
Think of it as the firm’s HubSpot, the shared support Gmail, or the operations Google Sheet. Harrington’s qualifying agent reads the shared calendar. A workflow scores a lead when a Sheet row appears. That is workspace, not Max.
You connect it the same way: pick the app, complete OAuth, then manage tools and scopes. The catalog looks familiar on purpose.
How is this different from a Max connector?
Who it belongs to. A Max connector is yours. A workspace connector belongs to the account. You can mark it shared, so anyone in the account can use it, or private, so only the person who connected it sees it.
Who consumes it. Max chat, Max playbooks, and Max tasks use Max connectors. Studio agents, agent playbooks, and workflows use workspace connectors.
Where triggers land. The same kinds of events exist on both sides. On Max they start a Max task. On the workspace they start a workflow. A new Gmail on your personal inbox can run a personal brief. A new Gmail on the firm inbox can run Lead Scoring.
Who can change tools. On a workspace connector, the creator, an admin, or an owner updates the alias, visibility, and enabled tools. Changing the tool list is account-wide. Every agent and workflow that uses “all tools” on that connection picks up the change.
How do tools, scopes, and MCP work here?
The same pattern as Max. Open the connector, open View tools, search the list, and enable the slugs you want. Scopes are the OAuth grant. A tool that needs a scope you did not grant will fail until you reconnect.
An AI node in a workflow can use every enabled tool on the connection, or a shorter list. The qualifying agent might get “create event” on the shared calendar. The collections workflow might get none of the calendar tools and only the billing ones.
What triggers can a workspace connector fire?
Workflows listen with an Event Trigger set to an integration event. New Gmail. New Sheet rows. HubSpot deal stage. Salesforce lead. Stripe payment. Drive file created. Outlook message or calendar change.
The event body arrives as {trigger_payload}. Downstream nodes extract what they need and write to People, Deals, or Tickets.
Harrington’s ops Sheet gets a new row when a mandate closes. A workspace Google Sheets connector fires the workflow. An AI Agent node writes the next review date on the Deal. That run is a workflow log, not a Max task.
Where should I start?
Connect the one shared system the team already treats as source of truth. Enable a tight tool list. Point one workflow at one event. Keep personal inboxes on Max connectors so James’s mail does not drive a firm-wide automation.