n-Nutshell Covers the Common Integrations. Specific Needs Still Need Custom Work.
Nutshell's native integrations cover a handful of the usual pairings, most notably Gmail and Google Workspace for two-way email sync, plus connections to common email-marketing tools, on top of a documented REST API for anything else. For the common case, that's usually enough. The moment a business needs a specific field mapped a specific way, or a tool outside that short native list, it becomes custom integration work against the API, which is what we build.
What connects to Nutshell natively
Nutshell's Gmail and Google Workspace sync is the most-used piece: emails sent and received through Gmail get logged against the right contact or company in Nutshell automatically, so a rep isn't manually forwarding messages into the CRM to keep a record current. Exactly which Google features are covered can change over time, so check Nutshell's current integrations list if you're relying on a specific piece of that sync.
Nutshell also connects to common email-marketing tools, so a contact's marketing-email activity can show up alongside their deal history instead of living in a separate platform nobody checks during a sales conversation.
Where the native connections stop
Native sync tends to cover the general case: log the email, sync the basic contact fields, show marketing activity. What it doesn't do is react to something specific happening in Nutshell and push it somewhere else automatically, a deal closing and creating an invoice, a lead score change feeding into a different tool, a support interaction updating the Nutshell record in real time.
That's where Nutshell's REST API comes in. It exposes contacts, companies, deals, and activities, which is exactly what we use to build the more specific connections native sync was never meant to handle.
Need Nutshell talking to something more specific than Gmail and your email tool?
Tell us which two systems need to stay in step and what should trigger the update. We'll map what's doable against Nutshell's API versus what the native integrations already cover. Nutshell handles the common pairings fine on its own, the specific ones are where custom work actually earns its keep.
Let's talk