Twenty + Outlook Integration
Twenty + Outlook integration logs emails, meetings, and calendar activity against your People and Company records automatically — no manual forwarding, no BCC habit to enforce. We configure Twenty's native Outlook sync where it fits, and build on Microsoft Graph and Twenty's REST/GraphQL API when your matching or routing rules go further.
What Does a Twenty + Outlook Integration Do?
Sales and account teams live in their inbox, but a CRM is only useful if that activity ends up on the record. A Twenty + Outlook integration matches incoming and outgoing email addresses against your People records and logs the thread automatically, so anyone opening a Twenty record sees the full email history without anyone having to remember to CC or forward.
Twenty ships native Outlook and Microsoft Calendar sync via Microsoft Graph: once a workspace member connects their Microsoft 365 account, matched emails and meetings appear on the record with no middleware required. For most teams, our job is configuring that sync correctly — matching rules, which folders are excluded, and which fields calendar events map to.
Where teams need more — shared mailbox routing, custom matching against secondary email addresses, or writing calendar events back into Twenty as structured Meeting or Task objects — we build on top of Microsoft Graph and Twenty's REST or GraphQL API and webhooks to fill the gap.
What Data Moves Between Outlook and Twenty?
Email Threads
Inbound & outbound messages
Matched to People and Company records and logged as timeline activity
Meetings
Outlook Calendar events
Attendees, time, and outcome notes tied to the relevant record
Attachments
Files sent over email
Referenced against the record so context isn't buried in a mailbox
New Contacts
Unrecognized senders
Optionally create a draft People record for review instead of a silent drop
How Do You Integrate Outlook with Twenty?
Most teams only need Twenty's native Outlook sync configured correctly. We reach for custom middleware on Microsoft Graph only when routing, matching, or write-back requirements go beyond it.
| Approach | What it is | Best for | Watch out for |
|---|---|---|---|
| Native Outlook & Calendar Sync | Twenty's built-in per-user Microsoft 365 account connection | Standard email & meeting logging with no custom logic | Matching rules and excluded folders need configuring per team |
| Microsoft Graph + Twenty REST/GraphQL | Custom middleware reading Outlook and writing structured Twenty records | Shared mailboxes, secondary-address matching, custom Meeting/Task creation | Requires app registration and OAuth consent — that's the trade-off for the extra control |
| Webhooks (Twenty side) | Push notification when a Twenty record is created or updated | Triggering a downstream email (e.g. a welcome sequence) off a new record | Still fetch the full record over the API after the ping |
The truth most vendors won't tell you: if you just need emails and meetings logged, Twenty's native sync is genuinely the right answer and costs nothing extra to run. We'll tell you when that's the case rather than pitching a custom build you don't need.
How Much Does a Twenty + Outlook Integration Cost?
A typical Twenty + Outlook integration costs between $900 and $8,000, depending on whether it's native sync configuration or a custom build.
| Approach | Implementation | Ongoing |
|---|---|---|
| Native Outlook/Calendar sync configuration | $900 – $2,500 | None — built into Twenty |
| Custom matching & routing on Microsoft Graph | $3,000 – $6,000 | Support retainer only |
| Shared mailbox / bi-directional activity sync | $5,000 – $8,000 | Support retainer only |
The number moves most on whether email is 1:1 per-user or a shared team inbox, how strict the matching rules need to be, and whether calendar events need to write back as structured Twenty objects rather than just appearing in the timeline. We quote a fixed price after a scoping call.
What Does Our Integration Process Look Like?
Every engagement follows the same five stages — you get a fixed-price scope and a mapping sheet you sign off before we build.
Discover
We map your inbox structure, team size, and the matching rules you need.
Map
We document every field, direction, and matching rule before building.
Build
We configure native sync or implement custom middleware against a sandbox workspace.
Test
We run real email and meeting scenarios end to end — false matches, edge cases, duplicates.
Support
We monitor after go-live, with alerting, logging, and a named contact.
The Team on Both Sides of the Sync
We're an official Twenty CRM partner, and we build and run integrations for companies across the US, UK, Australia, and India. We recommend native sync when it fits and build custom only when your inbox structure demands it — no reason to oversell you a service you don't need.
Outlook is one integration among several we connect to Twenty. See our full Twenty CRM integration services page, or explore other popular pairings like Stripe and Shopify.
Frequently Asked Questions
Yes. Once connected, inbound and outbound emails with a matching contact are logged to that person's Twenty record automatically, with no manual forwarding or BCC step needed.
Twenty ships native Outlook and Microsoft Calendar sync out of the box via Microsoft Graph. We configure and tune that native sync for most teams, and only build custom middleware on top of Microsoft Graph and Twenty's REST/GraphQL API when the matching, filtering, or field-mapping rules go beyond what native sync supports.
Yes. Alongside email, we sync Outlook Calendar events and meeting attendees onto the relevant Twenty People and Company records so meeting history sits next to the email thread.
Yes. Shared mailboxes need custom matching logic on Microsoft Graph since native sync is built around a single connected account — we scope this separately.
Configuring native Outlook sync typically costs $900 to $2,500. Custom email-matching logic, shared-mailbox routing, or bi-directional activity sync runs $3,000 to $8,000. We quote a fixed price after scoping.
Ready to Stop Re-Keying Email Activity into Twenty?
Every week without this integration, your team is manually logging or losing email context. A scoped Twenty + Outlook integration removes that work permanently — and you'll know the exact cost before we start.