IdentifyAI TRANSFORMATION
Identify Integrations

Keep your software.
Connect the AI layer.

Identify 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.

↔/
AUSTRALIA / APPLIED AI
THE INTEGRATION PRINCIPLE

We are not trying to replace anyone.

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.

BUILT INTO IDENTIFY OS

Start with the two productivity stacks most businesses already have.

DIRECT CONNECTION PATH

Google Workspace

Gmail, Calendar and selected Drive files through user-authorised access inside Identify OS.

OAUTH · USER CONTROLLED
DIRECT CONNECTION PATH

Microsoft 365

Outlook Mail, Calendar and OneDrive through Microsoft Graph and user-authorised access.

OAUTH · USER CONTROLLED
OPEN STANDARD

MCP

Remote Model Context Protocol servers provide a portable tool layer that can work across OpenAI and other compatible hosts.

APPROVAL-GATED BY DEFAULT
UNIVERSAL PATH

API + Webhook

For software with an API or webhook but no MCP layer, Identify can map the workflow without forcing a new system of record.

VENDOR-NEUTRAL
YOUR STACK

Examples, not partnerships.

These names illustrate the kinds of systems Identify is designed to work around. They do not imply commercial partnerships or certifications.

CRM & GROWTH
HubSpotSalesforceAttio
FINANCE
XeroMYOBQuickBooks
WORKFORCE
DeputyEmployment Hero
PROJECT & DELIVERY
ProcoreMondayAsana
COLLABORATION
SlackMicrosoft Teams
FILES & KNOWLEDGE
Google DriveSharePointDropboxOneDrive
EMAIL & CALENDAR
GmailGoogle CalendarOutlookMicrosoft Calendar
CHATGPT + MCP

Identify can be a tool inside the AI your team already uses.

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.

PUBLIC READ-ONLY MCP BETAhttps://identify.com.au/_api/mcp
EXPLORE IDENTIFY OS
LIGHTWEIGHT CONTROL

Open does not mean uncontrolled.

01

Keep the system of record

Identify sits above the software the business already trusts rather than forcing a migration into another closed ecosystem.

02

Use the most open path

Direct OAuth where useful, MCP where available, APIs or webhooks where they are the better engineering choice.

03

Read before write

Start with the least powerful useful access. Add write capability only when the workflow genuinely needs it.

04

Pause before side effects

External communications, edits and material actions stay approval-gated unless the customer deliberately changes the policy.

05

Own the operating layer

The customer keeps its vendor stack. Identify owns the workflow, agent definition, controls, evaluation and outcome model.

CONNECT ANYTHING USEFUL

Bring the stack you already have.

OPEN IDENTIFY OS TALK TO IDENTIFY