--- title: "Nutshell Integration" description: "Manage sales in Nutshell CRM through its JSON-RPC API: agents search people and companies by email before creating duplicates, open and advance leads through pipelines, log calls and meetings as activities, and read team, tag, and pipeline configuration." url: https://flowrunner.ai/integrations/nutshell date_modified: 2026-08-07T17:20:23-07:00 --- # Nutshell [CRM](https://flowrunner.ai/integrations/category/crm-sales) Manage sales in Nutshell CRM through its JSON-RPC API: agents search people and companies by email before creating duplicates, open and advance leads through pipelines, log calls and meetings as activities, and read team, tag, and pipeline configuration. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 22 actions · Basic auth · available [Nutshell website](https://nutshell.com/) · [Platform Documentation](https://developers.nutshell.com/) · Capability data verified 2026-07-27 1. A new paying customer lands in the storefront or billing system 2. Agent reads the signup's name, email, company, and order value 3. Search By Email confirms whether the person or company already exists in Nutshell 4. Agent links to the existing records, or runs Create Account and Create Contact for a genuinely new customer 5. Create Lead opens the opportunity with its value, confidence, and assigned rep 6. The rep gets a Slack summary with the new lead and its source 7. The rep confirms ownership and pipeline stage before the agent logs the first activity ## What This Integration Enables Nutshell is a CRM for small sales teams that live in the pipeline, not in report builders. That makes data hygiene the whole game: a pipeline with duplicates and ghost leads stops being trusted, and a CRM nobody trusts stops being used. FlowRunner agents work Nutshell's JSON-RPC API with the habits a careful rep would have. Search By Email runs before any record is created. Updates carry the record's current revision, Nutshell's optimistic concurrency check, so an agent can never silently overwrite an edit a rep made seconds earlier. From that base, agents sync customers and companies in from storefronts and billing systems, open and advance leads through pipelines resolved live from Get Pipelines and Find Stagesets, log calls and meetings as activities, and read an entity's full timeline before acting on it. Assignment stays grounded in the actual team via Find Users and Find Tags. ### Without FlowRunner **Duplicate people and companies**: Every inbound source creates its own copy of the same customer **Leads opened late**: Opportunities exist only after a rep notices the signup and types it in **Untracked touches**: Calls and meetings happen without ever landing on the record ### With FlowRunner **Email-first dedup**: Search By Email runs before any create, so records stay singular **Leads opened on arrival**: Create Lead fires with value, confidence, and owner the moment the signal lands **The timeline tells the story**: Create Activity and Find Timeline keep every touch on the record where the next rep can find it ## Use Case Scenarios ### Storefront Signup to CRM Record A new customer checks out in [Shopify](https://flowrunner.ai/integrations/shopify). The agent runs Search By Email against their address. If the shopper matches an existing contact or account, the agent attaches the purchase context there. If not, it runs Create Account for the company and Create Contact for the buyer, linked by id. Either way, the CRM gains exactly one clean record per customer, and no rep spent an evening merging duplicates. ### Payment Signal to Open Opportunity A deal signal fires upstream: a [HubSpot](https://flowrunner.ai/integrations/hubspot) deal is created, or a [Stripe](https://flowrunner.ai/integrations/stripe) payment intent completes. The agent opens the matching opportunity with Create Lead, setting the monetary value and linking the right contacts and accounts, then logs the originating interaction with Create Activity so the lead's first timeline entry explains why it exists. The rep opens Nutshell to a lead that already tells its own story. ### Pipeline Report Without the Export Ritual On a schedule, the agent pulls open opportunities with Find Leads filtered by status and milestone, appends each to a running sheet in [Google Sheets](https://flowrunner.ai/integrations/google-sheets), and posts a stage-by-stage summary to the sales channel in [Slack](https://flowrunner.ai/integrations/slack). When the numbers look off, the manager asks the agent for detail, and it answers from Get Lead and Find Timeline rather than from a stale export. ## Human-in-Loop Highlight Delete Lead is permanent. Nutshell removes the opportunity and returns only a boolean; there is no restore. So when the dedup agent finds two open leads tracking the same renewal, one owned by each of two reps, it does not pick a survivor. It gathers both records with Get Lead, pulls their histories with Find Timeline, and asks the sales manager in Slack: "Leads 4417 and 4522 both track the Acme renewal. 4417 has the signed quote activity; 4522 has the newer contact set. Which one survives?" The manager picks. The agent copies the missing context onto the survivor with Update Lead and Create Activity, then runs Delete Lead on the loser. A [human-in-the-loop](https://flowrunner.ai/concepts/human-in-the-loop) decision, because merging pipeline history wrong costs a rep their deal context. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via Slack Human decides Agent resumes with decision ## Agent Capabilities 22 actions ### Leads 5 - **Find Leads** Searches leads and returns matching stubs with id, name, status, and value. Filter by status, assignee, or milestone. The entry point for pipeline reporting and dedup sweeps. - **Get Lead** Retrieves a complete lead record: contacts, accounts, products, activities, and custom fields. Supports fetching a historical revision. - **Create Lead** Opens a new sales opportunity linked to existing contacts and accounts, with a monetary value, confidence percentage, and assigned owner. - **Update Lead** Updates a lead using its current revision for optimistic concurrency, so concurrent rep edits are never clobbered. Only supplied fields change. - **Delete Lead** Permanently deletes a lead. Cannot be undone, which is why dedup flows route this call to a human first. ### Contacts 4 - **Find Contacts** Searches people and returns stubs with id, name, and primary email, with ordering and pagination. - **Get Contact** Retrieves a complete contact: emails, phone numbers, linked accounts, and custom fields. - **Create Contact** Creates a person with name, email, phone, and description, optionally linked to an account. - **Update Contact** Updates a contact with revision-checked concurrency. Only supplied fields change. ### Accounts 4 - **Find Accounts** Searches companies and returns stubs by name, with ordering and pagination. - **Get Account** Retrieves a complete company record: contacts, leads, address, URL, and custom fields. - **Create Account** Creates a company with name, website, phone, and description. Its id anchors contacts and leads. - **Update Account** Updates a company with revision-checked concurrency. Only supplied fields change. ### Activities and Timeline 4 - **Find Activities** Searches logged calls, meetings, and events, with ordering and pagination. - **Get Activity** Retrieves one activity with its type, participants, linked records, note, and timing. - **Create Activity** Logs a call or meeting with type, subject, start and end times, and a note, linked to a lead. How agent-observed touches become CRM history. - **Find Timeline** Retrieves the chronological timeline for a lead, contact, or account: emails, notes, calls, and system events. Read this before acting on a record. ### Lookup and Configuration 5 - **Search By Email** Looks up the contacts and accounts tied to one or more email addresses. The dedup primitive that runs before every create, and the fastest way to identify who an inbound email belongs to. - **Find Users** Lists team members with id, name, and email. Grounds lead and activity assignment in the real roster. - **Find Tags** Lists defined tags, optionally scoped to leads, contacts, or accounts, for consistent categorization. - **Get Pipelines** Retrieves the configured sales pipelines and the stage groupings leads move through. - **Find Stagesets** Lists stagesets with their ordered stages. Resolve a lead's position from here instead of hardcoding stage names. ## Frequently Asked Questions ### What can FlowRunner do with Nutshell? FlowRunner agents can run Find Leads, Get Lead, and Create Lead in Nutshell, plus 19 more actions. ### Does connecting Nutshell to FlowRunner require OAuth? No. Nutshell connects to FlowRunner with basic authentication (a username and password), no OAuth flow required. ### Can Nutshell trigger a FlowRunner workflow automatically? Nutshell doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at Nutshell?** This integration exposes Nutshell to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/nutshell. Site index: https://flowrunner.ai/llms.txt