---
title: Nutshell API Integration on Truto
slug: nutshell
category: CRM
canonical: "https://truto.one/integrations/detail/nutshell/"
---

# Nutshell API Integration on Truto



**Category:** CRM  
**Status:** Generally available

## Unified APIs

### Unified CRM API

- **Accounts** — The accounts represent a company in a CRM.
- **Contacts** — The contacts represent an existing point of contact at a company in a CRM.
- **Engagement Types** — The engagement types represent an interaction activity in a CRM.
- **Engagements** — The engagements represent an interaction noted in a CRM.
- **Fields** — The fields of entities in a CRM.
- **Leads** — The leads represent a potential customer in a CRM.
- **Notes** — The notes represent a note on another object in a CRM.
- **Pipelines** — 
- **Stages** — The stages represent a stage of an opportunity in a CRM.
- **Users** — The users represent a user in a CRM.

### Unified User Directory API

- **Users** — The User object represents a User.

## How it works

1. **Link your customer's Nutshell account.** Use Truto's frontend SDK; we handle every OAuth and API key flow so you don't need to create the OAuth app.
2. **Authentication is automatic.** Truto refreshes tokens, stores credentials securely, and injects them into every API request.
3. **Call Truto's API to reach Nutshell.** The Proxy API is a 1-to-1 mapping of the Nutshell API.
4. **Get a unified response format.** Every response uses a single shape, with cursor-based pagination and data in the `result` field.

## Use cases

- **Log external communication touchpoints to Nutshell timelines** — If you build a sales dialer, SMS platform, or messaging tool, your users expect call logs, messages, and meeting notes to appear directly on their Nutshell contact and lead timelines. Offering this integration means their reps never leave Nutshell to check interaction history.
- **Automate deal progression from external workflow events** — E-signature, proposal, and billing platforms can move Nutshell leads through pipeline stages when external milestones occur — like a contract being signed or an invoice paid. This eliminates manual stage updates and keeps forecasting accurate for sales managers.
- **Sync contacts and accounts bidirectionally to eliminate duplicate data entry** — Any SaaS product that manages customer or company records — support desks, onboarding tools, event platforms — can pull and push contacts and accounts to Nutshell so sales reps always work from a single, up-to-date source of truth.
- **Enrich Nutshell records with product usage or intent signals** — Product analytics, PLG, and ABM platforms can write engagement flags and custom field values back to Nutshell accounts and contacts, giving sales reps the context they need to prioritize outreach and time upsell conversations.
- **Route and assign inbound leads from external capture tools** — Webinar, chatbot, and form-builder SaaS companies can create new contacts and leads inside Nutshell, assign them to the right sales rep via the Users model, and let Nutshell's native automation take over from there.

## What you can build

- **Automatic call and meeting logging** — Push engagements and notes — including call recordings, transcripts, and meeting summaries — to the correct Nutshell contact or lead timeline after every interaction.
- **Pipeline-aware document generation** — Pull lead, account, and pipeline stage data from Nutshell to auto-populate proposals or contracts, then advance the lead to a new stage when the document is signed.
- **Real-time contact lookup and screen pop** — Query Nutshell contacts on inbound calls or chats to surface account context, deal status, and recent notes before a rep picks up.
- **Custom field writeback for intent and usage data** — Update custom fields on Nutshell accounts and contacts with external signals like product usage scores, webinar attendance, or firmographic enrichment data.
- **Lead creation with rep assignment** — Automatically create Nutshell leads from external events — form fills, trial signups, demo requests — and assign them to the correct user by pulling the team roster from the Users model.
- **Bidirectional contact and account sync** — Keep your product's customer records and Nutshell's contact and account data continuously aligned, preventing duplicates and stale information on both sides.

## FAQs

### What Unified APIs does Truto support for Nutshell?

Nutshell is available through Truto's Unified CRM API (covering Accounts, Contacts, Engagement Types, Engagements, Fields, Leads, Notes, Pipelines, Stages, and Users) and the Unified User Directory API (Users). Specific tools are built on request — contact Truto to discuss your requirements.

### How does Nutshell's data model differ from a typical CRM?

In Nutshell, a 'Lead' represents a deal or opportunity that moves through a pipeline — not an unqualified person. People are stored as Contacts. Truto's Unified CRM API maps these correctly, but it's important to understand this distinction when designing sync logic.

### What authentication method does Nutshell use?

Truto handles authentication for Nutshell on your behalf. Your end users connect their Nutshell accounts through Truto's hosted auth flow, so you don't need to manage API keys, tokens, or credential storage yourself.

### Can I read and write custom fields on Nutshell records?

Yes. The Unified CRM API exposes a Fields model that lets you discover custom fields defined on Nutshell objects, then read and write values on Accounts, Contacts, and Leads as needed.

### Are Nutshell-specific tools available today or built on request?

Nutshell integration tools are currently built on request. The Unified CRM and User Directory APIs provide the standard models, and Truto's team will work with you to ensure coverage for any Nutshell-specific endpoints or behaviors your use case requires.

### How does Truto handle pagination and rate limits for the Nutshell API?

Truto abstracts away Nutshell's API-specific pagination and rate-limiting behavior. You interact with a consistent Unified API interface, and Truto manages retries, cursor-based pagination, and throttling behind the scenes.
