noCRM.io is a lead management software designed to help sales teams track and close deals efficiently.
noCRM.io is a lead management software designed to help sales teams track and close deals efficiently. On Nagent, NoCRM.io is exposed as a fully-configurable crm integration that any agent can call — 9 actions, and API key authentication. No code is required to wire NoCRM.io into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use NoCRM.io to automate the kinds of tasks crm teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire NoCRM.io into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against NoCRM.io, with input parameters and output schema. Drop these into any step of an agent built in Helix.
NOCRM_IO_ADD_A_TAG_TO_A_LEADTool to add a tag to a lead. Use when you need to assign one or more tags to a specified lead via noCRM.io.
Input parameters
Tag or comma-separated tags to add to the lead.
The unique identifier of the lead to add the tag to.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
NOCRM_IO_APPEND_TO_LEADS_DESCRIPTIONTool to append text to the lead's description. Use when you need to add context incrementally without overwriting. Example: Append 'Left voicemail' to lead 1234.
Input parameters
Unique identifier of the lead to update
Text to append to the lead's description. Cannot be used simultaneously with the `description` parameter.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
NOCRM_IO_ASSIGN_LEAD_TO_USERTool to assign a lead to a user. Use when reassigning a lead to the correct owner to trigger assignment notification.
Input parameters
Unique identifier of the lead to assign
ID or email of the user who will receive the lead
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
NOCRM_IO_CHANGE_LEAD_STATUS_CANCELLEDTool to change a lead's status to 'Cancelled'. Use after confirming no further follow-up is needed and the lead should be marked as cancelled.
Input parameters
The unique identifier of the lead to update
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
NOCRM_IO_CHANGE_LEAD_STATUS_STANDBYTool to change a lead's status to 'StandBy'. Use when scheduling follow-up after determining the next contact should occur in a set number of days.
Input parameters
Number of days to schedule the next reminder; must be a positive integer
The unique identifier of the lead to update
Optional activity ID to associate with the reminder
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
NOCRM_IO_CREATE_LEADTool to create a new lead. Use when adding a fresh prospect to your pipeline via noCRM.io. Example: Create a lead titled 'ACME Corp' assigned to a user.
Input parameters
Step's name for the lead.
Tags describing the lead.
Lead's title, usually corresponding to the company name.
Email address or ID of the user to assign the lead to. When using USER token, providing this yields an error.
Lead's description, typically containing contact information.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
NOCRM_IO_DELETE_LEADTool to delete a lead. Use when you need to permanently remove a specific lead after verifying it is no longer needed.
Input parameters
Unique identifier of the lead to delete
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
NOCRM_IO_DUPLICATE_LEADTool to duplicate a lead. Use when cloning an existing lead into a new step without overwriting original.
Input parameters
Name of the pipeline step for the new duplicated lead. Use after reviewing existing lead details.
Unique identifier of the lead to duplicate.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
NOCRM_IO_LIST_ALL_TEAMSTool to retrieve all teams. Use when you need to fetch every team and its members from noCRM.io.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 86 agents privately built on Nagent that already use NoCRM.io.
Build on Nagent
Connect NoCRM.io to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find NoCRM.io, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, NoCRM.io is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once NoCRM.io is connected, you configure its 9 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop NoCRM.io steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a NoCRM.io event fires, the agent kicks off automatically.
Every NoCRM.io action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While NoCRM.io ships with 9 pre-built crm actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching NoCRM.io together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build NoCRM.io-based workflows tailored to your business.