Loading tutorials…
Loading tutorials…
Email and calendar sync is what turns Attio from 'data entry' into 'background CRM' — emails auto-log, meetings auto-attach, interactions get tracked without anyone clicking. But default settings sync everything, including personal email. Here is the setup that earns rep trust on day one.
Who this is forOps leads rolling Attio out to a sales team — or any rep who connected their inbox, saw a personal email show up on a Company record, and disconnected immediately. If 'will my personal emails show up in the CRM?' is on the FAQ, this tutorial is for you.
What you'll need
Step 1
Attio reads emails from your connected inbox and matches sender/recipient addresses to existing People records. Matched emails get logged on the record automatically.
Connection: each rep authorizes their own Gmail or Outlook via OAuth. Attio does not get your password — it gets a scoped OAuth token.
Match logic: Attio scans the From, To, and Cc fields. If any address matches an existing Person record (by email), the email gets logged on that Person + any associated Company.
Unmatched emails: by default, emails to/from addresses that do not match any Person are NOT logged — they stay private in your inbox.
Sync scope: workspace settings define the default sync rules. Each user can override their personal settings.
Calendar sync works similarly — matched attendees become Interactions on records; unmatched events stay private.
Step 2
Workspace settings → Email settings → Sync defaults. Decide once what the team-wide default is before anyone connects their inbox.
Workspace settings → Email settings → Default sync rules.
Recommended starter scope: "Sync only emails where sender OR recipient matches an existing Person record." This is the privacy-first default.
For aggressive auto-logging: "Sync all emails and attempt to match" — Attio will log unmatched emails and prompt to create new People records. Riskier for personal email but more thorough.
Set domain filters: "Exclude emails to/from acme.com" if Acme is your own company (avoids logging internal email). Add personal domains to exclude (gmail.com if you do not want personal Gmail accounts to sync).
Set keyword filters: exclude emails with subject containing "Receipt," "Confirmation," etc. to avoid logging transactional noise.
Step 3
Do not announce "everyone connect your inbox today" without walking through what gets synced. Reps need to see the controls before they trust the sync.
Profile (top-right avatar) → Personal settings → Integrations → Email → Connect Gmail / Outlook.
Walk through the OAuth scopes: Attio requests Read email metadata + body, Send email on your behalf (for in-Attio sends), Read calendar events. Show reps the OAuth consent screen before they click.
After connection: open your sync settings → review what is being synced. Each rep should set their personal overrides: "Only sync emails with external contacts" is a common safe default.
Test: send a test email to a known Person record. Verify it logged. Send a test email to a personal contact. Verify it did NOT log.
For Gmail specifically: install the Attio Chrome extension. This gives inbox-side controls (log this thread, snooze, add to Attio) without leaving Gmail.
Step 4
Calendar sync uses different scopes than email. Often you want broader calendar sync (every meeting auto-logs) but tighter email sync (only matched emails log).
Personal settings → Integrations → Calendar → Connect Google Calendar / Outlook Calendar.
Scope: by default, all meetings with at least one external attendee log as Interactions on the matched Person + Company.
Exclude: internal-only meetings (where all attendees are on your domain) typically should NOT log. Set this in the calendar sync rules.
For Sales: enable "Auto-create Interactions for upcoming meetings" — Attio creates a placeholder Interaction record so reps see "Demo scheduled" on the timeline before the meeting happens.
Calendar sync makes the most visible difference in adoption — reps see meetings auto-populate on records and stop manually logging.
Step 5
Reps need to know how to (1) see what got synced, (2) exclude a specific thread, (3) disconnect entirely if they want to.
Train each rep on: Personal settings → Integrations → Email → View sync activity. Shows the last N emails Attio considered for sync, with reasoning (matched/unmatched).
Train: how to exclude a specific email or thread — open the email in Attio, click the "..." menu, "Exclude from sync." Useful for one-off sensitive threads.
Train: how to add an email to sync manually — from inside Gmail/Outlook, use the Attio extension to "Log to Attio" and pick the matching record. Useful when the auto-match missed.
Train: how to disconnect — Personal settings → Integrations → Email → Disconnect. Reassure reps this is a one-click revoke.
Document these controls in your team wiki. Refer to them in onboarding for every new hire.
Step 6
Sync can degrade silently — token expiration, scope changes, rate limits. Weekly check catches drift. Quarterly audit catches privacy creep.
Workspace settings → Email settings → Sync health. Look for users whose sync has been "Paused" or "Errored" for 24+ hours.
Common causes: OAuth token expired (rep needs to re-authorize), Workspace email policy changed, Inbox over the sync rate limit.
Quarterly: spot-check 5 random Person records. Are any logged emails clearly personal/private? Investigate workspace sync rules and tighten.
For sensitive industries (healthcare, financial services, legal): consider running email sync OFF by default and have reps use the manual "Log to Attio" flow. Trades some convenience for stronger privacy posture.
Common mistakes
Not excluding the internal email domain
What goes wrong: Every email between teammates (acme.com to acme.com) gets logged on a Person record. Sales managers see SDR's internal complaints on the deal timeline. Reps lose trust in the system within a week. Recovering trust costs weeks of side conversations and ~$200-400 of specialist time to reconfigure + relaunch.
How to avoid: Workspace settings → Email settings → Sync defaults → exclude your own email domain. Verify on a test internal thread before announcing.
Announcing "everyone connect their inbox" without training first
What goes wrong: Reps connect, see a personal email on a Company record, disconnect immediately. Adoption craters. Recovery takes months because reps now distrust sync entirely. On a 10-rep Pro workspace at ~$700/month, you are now paying full price for a feature 30% of the team has disabled — call it $200/month wasted plus the opportunity cost of lost interaction logs.
How to avoid: Run a 30-minute team kickoff: walk through OAuth scopes, the privacy-first defaults, and the personal sync controls. Connect during the call so questions get answered live.
Over-aggressive sync scope ("Sync all emails")
What goes wrong: Receipts, newsletters, internal threads, personal emails all log onto records. Person timelines become noise. Reps cannot find the actual sales emails amid the junk.
How to avoid: Stick with "Sync only emails matching existing People records" as the default. Add unmatched logging only after the team has weeks of trust.
Skipping calendar sync because "email sync was hard"
What goes wrong: Email auto-logs but meetings still require manual entry. Reps stop logging meetings; the Interaction timeline is half-empty; deal reviews miss context.
How to avoid: Calendar sync is usually less sensitive than email — fewer privacy concerns. Enable it during the same kickoff session.
Not monitoring sync health
What goes wrong: OAuth token expired 60 days ago. Rep's emails stopped syncing without warning. Pipeline reviews missed weeks of context. Discovered only when a manager asked 'why is nothing logged for this deal?' If the rep was working a $50K+ deal during the gap, the missing context can directly cost the close.
How to avoid: Weekly: Workspace settings → Email settings → Sync health. Email any user with errored sync. Add a meta-workflow to alert on errored sync if you have time.
Recap
Done — what's next
How to set up an Attio workspace without painting yourself into a corner
Read the next tutorial
Hand it off
Email + calendar sync is the highest-leverage adoption move in Attio — and the one most easily fumbled in a way that destroys rep trust. A specialist will configure the workspace defaults, run the team kickoff, set up the sync-health monitoring, and document the controls. Typically a one-shot $200-400 engagement.
See specialist rates
Only if you (or workspace admin) sync personal emails. The default privacy-first setup only logs emails where the sender or recipient matches an existing Person record in Attio — so personal contacts (not in the CRM) stay private. You can also exclude specific domains or threads. Disconnecting is one click.
Read email metadata + body (so it can match and log), Send email on your behalf (so in-Attio sends come from your inbox), and Read calendar events. Attio does NOT request: send/delete unrelated emails, modify your Gmail settings, access drafts you have not opened. The full OAuth consent screen is visible before you authorize.
Open the email inside Attio → click '...' menu → 'Exclude from sync.' Or from Gmail with the Attio extension installed → click the Attio icon in the inbox → 'Do not log this thread.' Exclusions are per-user and per-thread; they do not affect other users' sync.
When you first connect, Attio syncs the last 90 days by default (configurable up to 1 year on Pro). After that, real-time sync of new emails. Historical sync runs in the background over a few hours for most inboxes. You can disable historical sync to only log new emails going forward.
Yes — Attio recognizes Gmail aliases (you+tag@gmail.com) and the corresponding parent address. Configure aliases in Personal settings → Integrations → Email → Aliases. Useful for reps who use plus-addressing to track campaign sources.
Attio
Attio is the modern, fast, Notion-influenced CRM that B2B SaaS teams are picking when HubSpot starts feeling rigid. It's also easy to break in the first month — wrong workspace name, wrong currency, wrong member roles, wrong billing seat plan. Here is the setup sequence that holds up.
Attio
Attio Workflows are the operational core of the platform — assign owners, send Slack pings, update stages, sync to other tools. Build them carelessly and they fire 800 times the first weekend and you spend Monday unwinding. Build them with discipline and reps stop doing repetitive busywork. Here is the discipline.
Attio
Attio's API is the under-rated power of the platform. A clean REST surface, webhooks for every event, and OAuth for partner apps. Used right, it makes Attio the spine of your stack. Used wrong, it leaks tokens, double-writes records, and spirals rate-limit costs. Here is the discipline.
Attio
DIY Attio is a great idea — until it isn't. This is the honest framework for when the cost of self-managing exceeds the cost of hiring help, and how to tell which side you are on.