Google Workspace
Gmail, Calendar and selected Drive files through user-authorised access inside Identify OS.
OAUTH · USER CONTROLLEDIdentify OS is designed to work with the systems established businesses already use. OpenAI is the default intelligence layer. Google Workspace and Microsoft 365 have direct connection paths, while MCP, APIs and webhooks keep the architecture open to everything else.
A business may already have excellent finance, CRM, workforce, project, communication and industry software. Identify's job is to make the workflow intelligent across those systems, not convince the customer to abandon them.
If the software exposes a useful, secure integration path, it belongs in the Identify architecture.
Gmail, Calendar and selected Drive files through user-authorised access inside Identify OS.
OAUTH · USER CONTROLLEDOutlook Mail, Calendar and OneDrive through Microsoft Graph and user-authorised access.
OAUTH · USER CONTROLLEDRemote Model Context Protocol servers provide a portable tool layer that can work across OpenAI and other compatible hosts.
APPROVAL-GATED BY DEFAULTFor software with an API or webhook but no MCP layer, Identify can map the workflow without forcing a new system of record.
VENDOR-NEUTRALThese names illustrate the kinds of systems Identify is designed to work around. They do not imply commercial partnerships or certifications.
A public read-only Identify MCP beta now exposes the workflow library and function playbooks as tools. The next layer is authenticated workspace access so approved Identify OS actions can be initiated from ChatGPT without rebuilding the workflow somewhere else.
https://identify.com.au/_api/mcpIdentify sits above the software the business already trusts rather than forcing a migration into another closed ecosystem.
Direct OAuth where useful, MCP where available, APIs or webhooks where they are the better engineering choice.
Start with the least powerful useful access. Add write capability only when the workflow genuinely needs it.
External communications, edits and material actions stay approval-gated unless the customer deliberately changes the policy.
The customer keeps its vendor stack. Identify owns the workflow, agent definition, controls, evaluation and outcome model.