Push Website Leads Into Nutshell Automatically
Each capture creates a Contact in Nutshell and a Lead linked to it, described with where it came from. Connected with a single API key in about a minute.
How the Connection Works
Nutshell is the simplest connection of the five: no OAuth screens, no app installation. You generate an API key inside Nutshell, paste it into Site2CRM once, and the integration is live. The key is stored encrypted, and revoking it inside Nutshell shuts the connection off instantly.
Create an API key in Nutshell
In Nutshell, go to Settings, then API Keys, click New API Key, and name it something like Site2CRM.
Open Integrations
In Site2CRM, go to Integrations and choose Nutshell.
Paste and save
Enter your Nutshell email and the API key, then save.
Done
The integration shows Connected, Nutshell becomes your active CRM, and new leads sync from that moment on.
What Syncs to Nutshell
Contacts
Each captured lead becomes a Nutshell Contact with their name and email.
Leads
A Nutshell Lead is created and linked to the Contact, so it enters your sales process attached to a real person.
Source in the description
The Lead's description carries its origin, for example "Google Ads lead from jane@acme.com", so you can see where each lead came from.
Field Mapping
| Site2CRM field | Nutshell field |
|---|---|
| Name | givenName, familyName |
| Contact email | |
| Source | Lead description |
Phone, lead score, and full submission details stay on the lead in Site2CRM, where your team works the capture queue.
How duplicates are prevented
Deduplication happens at capture, before anything touches Nutshell. When the same email submits again within 24 hours, Site2CRM matches it to the existing lead instead of creating a new one, so repeat submissions do not multiply Contacts in your Nutshell account.
Reliability
Sync runs as a background job within seconds of capture, so your visitor never waits on the Nutshell API. Every lead is always stored in Site2CRM first, which means an API problem on the Nutshell side can never lose the lead itself; it stays in your Site2CRM queue either way.
How to Sync Website Forms to Nutshell Without Zapier
Getting website forms into Nutshell usually means a Zap and a hand-built payload. Here is the same job with the chain removed.
| Through Zapier | With Site2CRM |
|---|---|
| Your form plugin or form service captures the submission. | The Site2CRM form or AI chat agent captures the lead and stores it in Site2CRM first. |
| The Zap trigger picks the submission up. On polling triggers the wait depends on your Zapier plan. | The push to Nutshell starts the moment the form submission is accepted. There is no queue and no polling interval in between. |
| A Formatter step splits the full name into first and last. | The name is split before the push. Nothing to configure. |
| A Filter step decides whether the submission qualifies, and spam gets through whatever you did not filter. | Honeypot and rate-limited submissions are rejected at capture, and a repeat from the same email inside 24 hours updates the existing lead instead of creating a second one. |
| An action step creates the Contact. | The Contact is created. |
| A second action step creates the Lead and links it to the Contact. | The Lead is created, linked to the Contact, and described so the website origin is visible. |
| Every step in the chain counts as a Zapier task. | The lead counts once. |
- Nothing has to be rebuilt in Nutshell. Your pipelines, stages and reports stay exactly as they are.
- Setup is an API key, so there is no app to install and no OAuth approval to chase.
- You can keep Zapier for everything else. Site2CRM has its own Zapier app for the apps it does not integrate with natively.
Requirements
- A Nutshell account with API access
- A Nutshell API key (created in Settings, then API Keys)
- A Site2CRM Starter plan or higher (the free plan does not include CRM sync)
For teams that want zero ceremony
Nutshell attracts teams that picked their CRM for simplicity, and the integration matches that: one API key, no OAuth consent screens, no marketplace installs. Sixty seconds of setup, and website leads flow into the same simple pipeline your team already runs.
Frequently Asked Questions
Do I still need Zapier to connect my forms to Nutshell?
No. Site2CRM pushes to Nutshell directly, so there is no Zap to build and no polling interval between the form submission and the record. Zapier is still worth keeping for the apps we do not integrate with natively, and Site2CRM has its own Zapier app for exactly that.
Do I need OAuth or an app install?
No. Nutshell uses simple API key authentication. Generate a key in Nutshell under Settings and API Keys, paste it into Site2CRM, and you are connected.
What does a synced lead look like in Nutshell?
A Contact with the visitor's name and email, plus a Lead linked to that Contact whose description tells you where the lead came from.
Is my API key stored securely?
Yes. Credentials are encrypted at rest. And because it is your key, revoking it inside Nutshell cuts off access instantly.
Will repeat submissions create duplicate Contacts?
No. Site2CRM deduplicates at capture: a repeat submission from the same email within 24 hours updates the existing lead instead of creating a new one.
Do AI chat leads sync too?
Yes. Leads captured by your AI chat agent create the same Contact plus Lead pair as form submissions.
Keep Nutshell. Stop losing website leads.
Free plan available, no credit card required. Connect Nutshell in minutes.
Using a different CRM? See all integrations or connect through Zapier.
Other CRM integrations:HubSpot,Salesforce,Pipedrive,Zoho CRM