Docs / Workflows / Integrations
Integrations
A connection gives OAIZ access to an account in an external service, its actions and the events it publishes.
OAIZ uses connected Google accounts to run workflows configured by business customers. Gmail mailbox changes, Google Calendar event changes and Google Drive file changes can also start workflows. Each service below explains the Google permissions it requests and the actions those permissions enable.
Google data use and removal
The business customer controls workflows using the connected account. Google data can become input to an action that uses AI, such as LLM call, Agent or Decision. OAIZ sends that input to the LLM provider or TypeSafe AI decision engine used for the action to produce the requested output. OAIZ does not use Google data to train, fine-tune or improve AI models. OAIZ does not sell Google data or share it for advertising.
OAIZ stores connection credentials while services are connected. Google data can also be stored in workflow events, execution history and files. Removing a service does not erase these retained records. The privacy policy and Data Processing Agreement explain storage, sharing, retention and deletion. Contact the business customer or support@oaiz.io to request deletion of retained data.
Removing one Google service stops its OAIZ actions and subscriptions. Other services on the same account keep the shared connection and accumulated Google permissions. Removing the final service deletes the stored credential and requests revocation at Google. The disconnect result reports whether Google confirmed revocation.
OAIZ’s use and transfer of Google API data follows Google’s Limited Use requirements. For Gmail, Google Calendar and Google Drive, OAIZ also follows the additional requirements of the Google Workspace API User Data and Developer Policy described in the privacy policy.
Microsoft
Messages and customer conversations
Work and records
Data and monitoring
Connections and access
Each connection has its own account and permissions. Multiple connections to one provider can represent different mailboxes, workspaces or teams. A workflow uses the connection assigned to its action.
Only a connection’s Owner can reconnect, configure, remove or share it. An organisation Administrator does not automatically own every connection.
A grant’s role and tool selection limit the actions it allows. Provider permissions also apply. Removing a connection pauses live workflows that use it.
Custom integrations
A custom integration connects your own HTTPS API or an MCP server. Its actions work in jobs like those of any other integration, and your systems can send events through it.