Delivery coordination is a retrieval problem before it is a writing problem: what changed, what is blocked, and what was promised. This guide maps those questions to connector categories and shows precisely what Connector Scout has verified for each AI platform. Write capabilities matter here more than anywhere else, because a task created by mistake is visible to the whole team.
●16 published connectionsLast verified Not recordedBy Connector Scout editorialReviewed by Connector Scout research desk◌Research in progress
The template and every verified fact below are live, but this page does not yet meet the publication threshold. Outstanding requirements:
Editorial status is "draft", not published.
0 of 2 required workflows whose connections are all published.
Publication date is missing.
Last-verified date is missing.
Last-researched date is missing.
The short answer
For project managers the important categories are project management and issue tracking (the system of record), communication (the blockers that never reach the tracker), calendar and email (coordination), and knowledge management (plans and notes). Read access covers most of the value; write access is where the risk concentrates, so treat it as a separate decision with its own approval.
What this guide covers
This guide covers connectors that link AI platforms to the applications and data sources used in this profession. It does not rank standalone AI tools or general-purpose AI software.
What this role needs from a connector
Each responsibility maps to a connector category and the capability a connection must document before it can help.
Responsibilities of a project manager, the connector category each one depends on, the capability required, and any verified example connections.
Connector Scout has published 6 verified connections relevant to this role on ChatGPT. OpenAI's assistant, extended through connectors that bring workspace data into a conversation and through apps built on the Apps SDK.
Connector Scout has published 6 verified connections relevant to this role on Claude. Anthropic's assistant, extended through first-party connectors and through custom connectors backed by remote MCP servers.
Connector Scout has published 4 verified connections relevant to this role on Gemini. Google's assistant, where access to business data is governed largely by Google Workspace administration rather than by an in-product gallery.
Status writes require separately verified capabilities
Cross-project visibility must be managed deliberately
How to choose
Begin with the platform the organisation has standardised on
Coverage for task systems differs sharply between assistants, and the licence you already hold usually decides the shortlist.
Treat write access as a separate approval
Reading status is low-risk. Creating or transitioning work items changes shared state and deserves its own decision.
Scope to a project space, not the workspace
Workspace-wide indexing pulls in archived, confidential, and cross-client material that has no place in a status update.
Knowledge managementProject management
Confirm calendar scope before connecting
Calendar connections often expose attendee lists and event titles across every calendar the account can read.
Calendar
Check administrator requirements early
Task tools are usually org-managed, so the connection is enabled centrally rather than by the project manager.
Prefer verified native connections for recurring reporting
A weekly ritual built on an unmaintained third-party implementation fails at the worst moment.
Security and data-access considerations
Project plans routinely contain client-confidential scope, pricing, and delivery risk.
Spaces used for delivery often also hold performance or personnel discussion that should not be connected.
Meeting notes capture opinions that read very differently when summarised out of context.
Cross-project access is easy to grant accidentally when a workspace-wide connection is enabled.
Accidental task creation or status changes are the most common practical harm from a write capability.
Under research
These pairings exist in the dataset but carry no published availability, capability, plan, or setup claim. They are excluded from every count and recommendation on this page.