Gmail & Outlook

Connecting Gmail or Outlook lets Pact send sequence emails from your real inbox and automatically detect replies — so steps 2, 3, and beyond fire only when the contact has not already responded.

What the integration does

• Send from your address — sequence emails appear in the contact's inbox as coming from you, not from a generic ESP domain.
• Reply detection — when a contact replies, Pact marks the sequence step as replied and pauses further steps.
• Thread matching — Pact uses the References and In-Reply-To email headers to match replies to the correct contact and sequence step.
• Sent-mail sync — sent emails are logged in the contact's activity feed.
• Calendar links — if you use Google Calendar or Microsoft Bookings, you can insert a scheduling link into sequence steps.

Connecting Gmail

1. Go to Settings → Integrations → Gmail.
2. Click Connect Gmail — you will be redirected to Google's OAuth consent screen.
3. Grant the Gmail Send and Gmail Readonly permissions. Pact requests the minimum scopes required.
4. After authorizing, you are redirected back to Pact. Your connected address appears in the integration settings.

Pact stores an OAuth refresh token, not your password. You can revoke access at any time from your Google account's security settings.

Google Workspace (GSuite) considerations

If your organization manages apps via Google Workspace admin, your IT admin may need to allowlist Pact's OAuth client ID before individual users can connect. The client ID is shown on the Gmail integration settings page.

Connecting Outlook / Microsoft 365

1. Go to Settings → Integrations → Outlook.
2. Click Connect Outlook — you will be redirected to Microsoft's OAuth consent screen.
3. Grant the Mail.Send and Mail.ReadWrite permissions.
4. After authorizing, return to Pact. Your connected address appears in the integration settings.

If your organization uses Conditional Access or requires admin consent for third-party apps, your IT admin must approve the Pact app in the Azure AD enterprise applications panel before OAuth will succeed.

Sending from a shared inbox or alias

Both Gmail and Outlook support sending from aliases. After connecting the primary account, add aliases in Settings → Integrations → [Gmail/Outlook] → Send-As Aliases. Pact will send using From: <alias> while authenticating with the primary account credentials.

Reply detection latency

Replies are checked every 5 minutes. If a contact replies between the check interval and the next scheduled step, the step may still send. To reduce false follows-up, set your sequence step delays to at least 30 minutes.

Inbox permissions and privacy

Pact reads only emails that match sequence threads it sent. It does not have access to your full inbox. The OAuth scopes grant Gmail Readonly (not Gmail Modify), so Pact cannot delete or move messages on your behalf — it can only read them to detect replies.

If you want to disconnect Pact from your inbox, go to Settings → Integrations → [Gmail/Outlook] and click Disconnect. This stops reply detection immediately; any in-flight sequences will continue sending until paused.

Troubleshooting

Sequences not pausing after a reply

Check that the connected email address matches the one you are sending from in the sequence. If you recently changed your send-from address, reconnect the integration.

"Access denied" during OAuth

Your Google Workspace or Microsoft 365 admin may have restricted third-party OAuth. Contact your IT admin and share the OAuth client ID shown on the integration settings page.

Emails landing in spam

Pact sends via the Gmail/Outlook API, so your inbox's reputation applies. Warm up new accounts gradually and avoid sending to unverified lists. See Importing data for consent guidance.