# Nutshell integrations: leads and contacts

> Create a lead, create a contact and create an activity in Nutshell, and start a workflow when Nutshell sends “Contact edited”.

**Canonical page:** https://tray.ai/connectors/nutshell-integrations/
**Categories:** Sales
**Connects through:** HTTP Connector

## Overview

Nutshell is a CRM for small sales teams that tracks leads, companies, people, activities and pipelines, with quotes, invoices and email marketing audiences alongside. Tray.ai connects to Nutshell through the HTTP Connector, so your workflows can call the Nutshell API alongside the rest of your stack.

## Use cases

### Leads

Read, create, update, and delete leads in Nutshell from any Tray.ai workflow. The Nutshell API covers calls such as list leads and get a lead.

- List leads
- Get a lead
- Create a lead

### Accounts

Read, create, and update accounts in Nutshell from any Tray.ai workflow. The Nutshell API covers calls such as list accounts and get an account.

- List accounts
- Get an account
- Create an account

### Contacts

Read, create, and update contacts in Nutshell from any Tray.ai workflow. The Nutshell API covers calls such as list contacts and get a contact.

- List contacts
- Get a contact
- Create a contact

### Activities

Read, create, and update activities in Nutshell from any Tray.ai workflow. The Nutshell API covers calls such as list activities and get an activity.

- List activities
- Get an activity
- Create an activity

### Tasks

Read, create, and delete tasks in Nutshell from any Tray.ai workflow. The Nutshell API covers calls such as list tasks and create a task.

- List tasks
- Create a task
- Delete a task

### Nutshell events

Start a Tray.ai workflow the moment something happens in Nutshell. Nutshell sends events such as contact edited and lead won to a Tray.ai webhook trigger.

- Contact edited
- Lead won

## Challenges Tray.ai solves

### Keeping Nutshell credentials out of logs

A raw API call usually means pasting a key or token into the request, where it ends up in step inputs, logs, and screenshots.

**How Tray.ai helps:** Store Nutshell credentials once as a Tray.ai authentication and reference them from the HTTP Connector. Tray.ai masks authentication values in logs, so the secret never shows up in a step's input or output.

### Going from the Nutshell API docs to a working call

Translating an example request from API docs into a workflow step means copying the method, URL, headers, and body by hand.

**How Tray.ai helps:** Paste a cURL example from the Nutshell API docs into the HTTP Connector and Tray.ai fills in the method, URL, headers, and body for you.

### Handling files and non-JSON responses

Not every API answers in JSON. Some return XML, files, or binary data, or expect a multipart upload.

**How Tray.ai helps:** The HTTP Connector parses JSON and XML responses, returns files you can pass to the next step, and sends multipart form data for uploads.

## Frequently asked questions

### Does Tray.ai connect to Nutshell?

Yes. Tray.ai connects to Nutshell through the HTTP Connector, which calls the Nutshell API directly. Any call the Nutshell API documents can run as a step in a Tray.ai workflow.

### How does Tray.ai authenticate with Nutshell?

The Nutshell API uses basic authentication. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated Nutshell connector?

Nutshell runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated Nutshell connector from the Nutshell API.

## Learn more

- Intelligent Integration: https://tray.ai/platform/intelligent-ipaas/
- Merlin Agent Builder: https://tray.ai/platform/merlin-agent-builder/
- Agent Gateway for MCP: https://tray.ai/platform/agent-gateway/
- Book a demo: https://tray.ai/contact/