Email integrations
Gmail and Microsoft 365 connections: purpose, prerequisites, permissions, sync behaviour, failure states, and what data is retained - the business effect without internal wiring diagrams.
Integrations
Purpose & scope
Gmail and Microsoft 365 integrations bring deal-linked email into Harold so decisions are not made from orphaned threads. The business effect is faster triage, clearer attribution, and fewer “who had the last version?” moments - not a dump of sync engine internals.
Rollout
Prerequisites
Before you connect
- Administrator consent for the relevant OAuth scopes in your tenant.
- A clear mapping of which mailboxes or shared accounts represent mandates.
- A support path for rotating credentials without disrupting live deals.
Permissions & data
Permissions determine which threads can be linked to which deals. Data retained in Harold should align to your retention programme; only the minimum necessary content is stored to support operational outcomes. Exact field-level transforms and queue topology are intentionally omitted from public documentation.
Operations
Failures & recovery
Integrations can pause when tokens expire, scopes change, or upstream providers throttle traffic. Operators should see actionable status; administrators should have a runbook to restore service and to communicate impact to deal teams without exposing internal retry schedules.
Was this page helpful?