Docs
Integrations
Your agents work inside the systems you already run, and you decide how much of each system Arzana can touch.
| Option | How it works |
|---|---|
| Forwarding | You forward the emails the agent needs (by rule or by hand) to a dedicated Arzana address. Arzana holds no credential to your mailbox |
| Microsoft 365 connector | Arzana reads the mailbox through a connector scoped to the minimum permissions the agent needs |
| Google Workspace connector | The same, through the Gmail permissions the agent needs and no more |
ERP and other business systems
| Option | How it works |
|---|---|
| No write access | The agent produces an import-ready file in your system’s own format, and your team imports it |
| Read-only access | The agent can look things up in your system but cannot change anything |
| Scoped write access | The agent can write exactly the records it needs, with no delete, admin, or schema rights |
Integration credentials are stored in AWS Secrets Manager, and we maintain each integration as part of your subscription, including any rework when you upgrade a connected system.
Systems we connect to
ERPs including Epicor, JobBOSS, E2, Plex, Infor, IQMS, Label Traxx, Global Shop, Prophet 21, Microsoft Dynamics, SAP, NetSuite, Sage, QuickBooks, and IFS; CRMs including Salesforce, HubSpot, Pipedrive, and Zoho; and Gmail and Outlook. If yours is not listed, we build the connection.
Changing or removing access
Tell your named engineer before you change a connected system, such as an ERP upgrade or a new mailbox, so the agent keeps working. You can also end Arzana’s access from your side at any time: remove the forwarding rule, revoke the connector in your Microsoft 365 or Google admin console, or disable the Arzana user in your ERP.