Integrations

Gmail and Google Workspace today, connected through Google's official OAuth consent flow — never your password. Monty sends from your real address through your own mailbox, never a relay domain, so your reply arrives from the person your lead already knows. Microsoft Outlook and Microsoft 365 / Exchange Online support is built but not switched on yet, and self-hosted/on-prem Exchange and plain IMAP mailboxes aren't supported; contact us if any of those is a blocker and we'll tell you honestly where it sits on the roadmap.

Read, send, and manage messages on the specific mailbox you connect — that's what lets Monty see incoming lead replies, place drafts or sends in the thread, and keep it organized. It does not request access to your contacts, files, or any other mailbox in your organization, and the mailbox connection never asks for calendar access (if you later enable meeting booking, that's a separate calendar-only consent you approve explicitly). You can see the exact scopes on the provider's consent screen before you accept, and revoke them at any time from your Google account security page.

HubSpot and Salesforce. Once connected (Settings → Integrations), Monty keeps contacts in sync and writes its key conversation signals back to the matching contact as notes, so your CRM stays the system of record without manual entry. Field updates are conflict-guarded so the sync can't silently overwrite records your team owns.

Work through these in order:

1. 1Clicking the Outlook button? Outlook sign-in isn't available yet — Microsoft support is built but not switched on, so it fails with “sign-in isn't available yet — the provider is not enabled for this environment”. That one is on us, not your browser: use Google or email sign-in for now and tell us at hello@montyai.co if Outlook is your setup.
2. 2For Google: check whether your company admin restricts third-party OAuth apps. Your Google Workspace admin may need to approve Monty before consent succeeds; that's a one-time approval on their side.
3. 3Make sure your browser isn't blocking cookies or redirects. Signing in with Google sends you to Google in the same tab and back again; when you're connecting a mailbox, the consent screen opens in the same tab or a new one depending on where you connect from, so allow pop-ups for montyai.co if nothing appears.
4. 4Retry once, in case the provider was briefly unavailable.
5. 5Still stuck, or seeing a plain-text error page instead of the provider's consent screen? That's on us — email hello@montyai.co with a screenshot and the time it happened, and we'll trace it.

Yes, and it's immediate: Settings → Integrations → Disconnect stops all reading and sending on that mailbox the moment you click, and removes the stored credentials. Revoking Monty's access from your Google account security page stops Monty renewing access from the provider's side, and any session already in flight ends within the hour. Your conversation history in Monty stays intact either way, so reconnecting later picks up where you left off.

Yes, as long as the shared address is a real mailbox someone can sign in to — a Google Workspace user account for sales@yourcompany.com, for example. Connect it like any other mailbox and its drafts land in the same approval queue, visible to your workspace for review. Each approval is attributed to the person who made it, so you keep accountability even on a shared address. Microsoft 365 mailboxes — shared or otherwise — can't be connected yet (Microsoft support is built but not switched on); tell us if that's your setup and we'll say honestly where it sits on the roadmap.