Skip to content

Nexus CRM

Nexus CRM runs fixed flow steps on the Nexus CRM: search for a contact, read their full record, look up a salesperson’s deals, log a call, add a note or a follow-up task, or propose a new deal. With a single component you work with contacts, company accounts, deals and activities.

The component works as the person who signed in on the credential: it only sees what that person sees in Nexus (a salesperson, their own deals) and whatever it records is in their name.

When to use it

  • After a meeting, an agent summarises the transcript and you want to log the interaction and the next step in Nexus.
  • Every morning you want to send a salesperson the summary of their open deals.
  • When a customer’s email arrives, you want to add a note to their record or create a follow-up task.
  • You want to propose a new deal from an automation and have a salesperson approve it.

Configuration

You need an MCP Remote server credential connected to Nexus’s MCP server with your sign-in. See Credentials and Use MCP servers.

  1. Create an MCP Remote server credential.
  2. In MCP Server url type your Nexus address followed by /api/v1/mcp, for example https://nexus.your-company.com/api/v1/mcp.
  3. In MCP Server auth choose OAuth2.1 and click the sign-in button.
  4. Sign in to Nexus with your account. Nexus asks you what NappAI can do: Read only or Read and work. To log notes, interactions, tasks or deals, choose Read and work, and click Authorize.
FieldWhat it does
Credential (required)The MCP Remote server credential with your Nexus sign-in.
MCP server URLFilled in by the credential: the Nexus address or its MCP server address (the one ending in /api/v1/mcp).
ResourceWhat you work with: Contacts, Accounts, Deals or Activities. Default: Contacts.
OperationWhat you do. The list changes with the chosen Resource. See Resources and operations.

IDs are the numbers Nexus uses, for example 1532. #1532 is accepted too.

Resources and operations

Contacts

OperationWhat it doesFields
Search ContactsSearches contacts by name, email or company.Optional: Search and Limit (default 20, at most 500).
Get ContactReturns a contact’s full record (their 360 view).Contact ID
Contact TimelineReturns a contact’s history: interactions, notes, tasks and deals.Contact ID

Accounts (company accounts)

OperationWhat it doesFields
Get AccountReturns a company account’s full record.Account ID

Deals

OperationWhat it doesFields
List My DealsReturns the deals of the person who signed in.Optional: Status (Any, OPEN, WON or LOST), Search (text in the title), Stage ID and Limit (default 20, at most 50).
Get DealReturns one deal.Deal ID. Optional: With activities, to also return its activities and next steps.
Pipeline SummaryReturns the sales pipeline’s stages with their ID and their totals.
Create DealProposes a new deal for a contact.Title, Contact ID. Optional: Amount, Expected close and Stage ID.
Update DealProposes changing a deal’s title, amount or expected close date.Deal ID and at least one of Title, Amount or Expected close.
Move Deal StageProposes moving a deal to another open stage.Deal ID, Stage ID
  • Amount is the amount in the company’s currency, for example 1500. 1.500,50 or 1,500.50 are understood too.
  • Expected close is a date such as 2026-12-15.
  • Stage ID is the ID of an open stage. Pipeline Summary returns it.

Activities

OperationWhat it doesFields
Add NoteAdds a note to a contact.Contact ID, Note (up to 20,000 characters).
Log InteractionLogs a call, a meeting or a demo with a contact, and its outcome.Contact ID, Summary and outcome. Optional: Type and When.
Add TaskCreates a follow-up task for a contact.Contact ID, Title. Optional: Kind, Details, Deal ID and Due.
Add Next StepAdds a next step to a deal.Deal ID, Title. Optional: Type, Details and Due.
  • In Log Interaction, Type can be CALL (default), MEETING, DEMO, PRESENTATION, EMAIL or OTHER. When is the date and time it happened.
  • In Add Task, Kind can be OTHER (default), CALL, EMAIL, LINKEDIN or MEETING. Deal ID links the task to a deal.
  • In Add Next Step, Type can be TASK (default), CALL, MEETING, EMAIL or NOTE.
  • Due is the due date and time, for example 2026-11-20T10:00:00Z.

Output

The Data output returns Nexus’s answer as data: one item per contact or deal in searches and lists, and the record, the confirmation or the change proposal in the others.

The component can be connected to an Agent as a tool for a specific action. See Tools. If you want an agent to use the whole CRM, use Nexus MCP.

Example

A sales team wants every meeting logged in Nexus without typing it by hand.

  1. The flow receives the meeting transcript and an agent summarises it, with the customer’s email and what was agreed.
  2. Add Nexus CRM with the Contacts resource and the Search Contacts operation, with the customer’s email in Search.
  3. Connect a second Nexus CRM with the Activities resource and the Log Interaction operation: in Contact ID the id of the contact found, MEETING in Type and the summary in Summary and outcome.
  4. If a next step was agreed in the meeting, add Add Task with the title and the due date.

Good practices

  • Search first and pass the numeric ID: operations don’t accept names instead of IDs.
  • Use the right person’s credential: the flow will see and record what that person would see and record.
  • If the connection with Nexus stops working, edit the credential and click Revalidate to sign in again.

Security and limitations

  • Nexus doesn’t allow closing deals (winning or losing them) from outside: Move Deal Stage only moves to open stages.
  • Creating, editing or moving a deal always needs a person’s approval in Nexus, within 10 minutes.
  • If you chose Read only when signing in, the operations that record something fail. Sign in again with Read and work.
  • You can withdraw NappAI’s access in Nexus, under My profile › Connections › AI assistants.