> ## Documentation Index
> Fetch the complete documentation index at: https://docs.atako.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# noCRM.io

> Connect noCRM.io to your Atako agents — 10 read and 7 write actions.

Let your agents work in your noCRM.io prospecting CRM: list and read leads, pipelines, steps, users, client folders, activities and lead comments, create and update leads, change their status, move them between steps, assign them, file them in a client folder and add comments.

## Connection

* **Authentication**: API key (noCRM.io API key).
* **Required settings**:
  * **noCRM subdomain** — acme in acme.nocrm.io (letters, digits, hyphens; no dot).

> [!NOTE]
>
> In noCRM.io: Admin panel → Integrations → API & automations → API Keys → create a key (name, description) and copy it. An account key has admin rights over the whole account. The API subdomain is the first part of your noCRM address (acme in acme.nocrm.io). Daily request limits depend on your account: see nocrm.io/api.
>
> See [noCRM.io's documentation](https://www.nocrm.io/api).

## Read actions (10)

| Action | Description |
| - | - |
| `get_client_folder` | Get one client folder: name, description, owner, extended\_info. id (integer, required, from list\_client\_folders). |
| `get_lead` | Get one lead: title, description (contact details), status, step, amount, probability, reminder, tags, owner, team, client folder and extended\_info. id (integer, required, from list\_leads). |
| `list_activities` | List the activity types (Call, E-mail, Meeting…): \[\{id, name, kind, parent\_id, …}]. The id is the activity\_id of reminders and comments. No arguments. |
| `list_client_folders` | List the client folders: \[\{id, name, description, is\_active, user\_id}]. The id is the client\_id of add\_lead\_to\_client\_folder. Optional order ("name" default or "id") and direction ("asc" default or "desc"). |
| `list_lead_comments` | List the comments of a lead: \[\{id, content, created\_at, user, activity\_id, is\_pinned, …}]. Arguments: lead\_id (integer, required, from list\_leads); direction ("asc" or "desc", default desc = newest first). |
| `list_leads` | List leads (the unassigned ones only with include\_unassigned). The total count is in the X-TOTAL-COUNT header. All arguments optional: limit (integer, default 100); offset (integer, default 0); order (string: id, creation\_date, last\_update, next\_action, sale\_step, amount, probability, probalized\_amount or alphabetically; default id); direction ("asc" or "desc", default desc); status (array of strings among todo, standby, won, lost, cancelled); step (string: step names separated by commas, OR step ids separated by commas, never mixed; names must match exactly, see list\_steps); starred (boolean, true = starred leads only); user\_id (string or integer: user id or e-mail, from list\_users); email (string: leads whose description or comments contain this address); tags (array of strings: leads having all of them); updated\_after (string, date or date-time); start\_date and end\_date (strings, dates) with date\_range\_type ("creation" default, "update", "next\_action" or "closed"); include\_unassigned (boolean, default false). |
| `list_pipelines` | List the pipelines: \[\{id, name, is\_default}] (a single one when multiple pipelines are not enabled). No arguments. |
| `list_steps` | List the steps of all pipelines: \[\{id, name, position, pipeline\_id, pipeline}]. The id or exact name is the step argument of create\_lead and update\_lead. Optional direction ("asc" or "desc", default asc, by position). |
| `list_users` | List the users of the account (deleted ones included, is\_disabled = true): \[\{id, firstname, lastname, email, is\_admin, …}]. The id or e-mail is the user\_id of the lead actions. All arguments optional: email (string); lastname (string); firstname (string); status ("all", "activated" or "deactivated", default all); role ("all", "admin" or "non-admin", default all); direction ("asc" or "desc", default asc, by id). |
| `ping` | Check that the API key works: \{status: 200, message}. Also used as the credential probe. No arguments. |

## Write actions (7)

| Action | Description |
| - | - |
| `add_lead_comment` | Add a comment to a lead; returns it with its id. Arguments: lead\_id (integer, required, from list\_leads); content (string, required); user\_id (optional, integer id or string e-mail of the author, from list\_users; omitted = the key's default author); activity\_id (optional, integer, from list\_activities). |
| `add_lead_to_client_folder` | File a lead in a client folder. Arguments: id (integer, required, lead id from list\_leads); client\_id (integer, required, from list\_client\_folders). |
| `assign_lead` | Assign a lead to a user (the user is notified by e-mail if enabled in their preferences). Arguments: id (integer, required, from list\_leads); user\_id (required, integer id or string e-mail, from list\_users). |
| `create_client_folder` | Create a client folder; returns it with its id. Arguments: name (string, required); description (string, optional); user\_id (optional, integer id or string e-mail of the owner, from list\_users). |
| `create_lead` | Create a lead; returns it with its id. Arguments: title (string, required, usually the company name); description (string, required, usually the contact as "Label: value" lines, e.g. "Firstname: John\nEmail: [john@acme.com](mailto:john@acme.com)"); user\_id (optional, integer id or string e-mail of the owner, from list\_users; omitted = unassigned, notification-free direct assignment); tags (optional, array of strings, created if missing); step (optional, string name or integer id from list\_steps, only applied when the lead is assigned; an unknown step answers 404). |
| `update_lead` | Update a lead: only the arguments sent change. id (integer, required, from list\_leads); then any of title (string); description (string, replaces the whole description; never together with append\_desc); append\_desc (string, added at the end of the description); amount (number); probability (number, percent); starred (boolean); step (integer id or string exact name, from list\_steps; unknown = 404); user\_id (integer id or string e-mail, assigns the lead; prefer assign\_lead to notify the user); tags (array of strings, created if missing); estimated\_closing\_date (string, YYYY-MM-DD, account time zone). On an UNASSIGNED lead only title, description and user\_id are applied, the rest is ignored. Status and reminders: use update\_lead\_status. |
| `update_lead_status` | Change the status of a lead and/or set its reminder. id (integer, required, from list\_leads); status (string: todo, standby, won, lost or cancelled; required); remind\_date (string, YYYY-MM-DD, account time zone; REQUIRED when status is "standby"); remind\_time (string, HH:MM, 24h, quarter hours); reminder\_duration (integer minutes among 0, 15, 30, 45, 60, 90, 120, 150, 180, 240, 480, 720); reminder\_activity\_id (integer, from list\_activities); reminder\_note (string). |

## Permissions

Every action above must be explicitly granted to an agent before it can be used. See [Permissions](https://docs.atako.ai/integrations/permissions.md) for the grant model and [Security](https://docs.atako.ai/integrations/security.md) for how credentials are protected.

***

*Last reviewed against the provider API: October 2026.*


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.