> For the complete documentation index, see [llms.txt](https://docs.stackai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackai.com/integrations/catalog/nocrm.io.md).

# noCRM.io

Create and manage sales leads and prospecting lists in noCRM.io.

### Connectors

Choose the connector that matches your authentication method. The options below use the names shown in StackAI.

| Connector | Authentication |
| --------- | -------------- |
| noCRM.io  | API Key        |

#### noCRM.io

Connect to noCRM.io with an account subdomain and API key.

**Set up in noCRM.io**

1. Prepare the noCRM.io account or service that the workflow will access. Grant access to the required resources and operations.
2. **API Key:** Copy the account API key from noCRM.io.

**Set up in StackAI**

1. Open **Settings → Connections**, add a connection, and select **noCRM.io**.
2. Enter the credentials and connection details in the fields below.
3. Save the connection and check its connection status. Select this saved connection when configuring an action or feature that uses it.

**Connection fields**

| StackAI field     | Required | What to enter                                                                                             |
| ----------------- | -------- | --------------------------------------------------------------------------------------------------------- |
| Account subdomain | Yes      | For <https://acme.nocrm.io>, enter acme.                                                                  |
| API Key           | Yes      | Copy the account API key from noCRM.io. [Provider instructions](https://www.nocrm.io/api#authentication). |

#### Verify the connection

Check that the connection is healthy. Then run a read operation against a resource the connected account can access. A successful connection check confirms authentication; it does not guarantee permission for every action.

If access is denied, check the credential or OAuth permissions, the selected account or environment, and access to the specific resource. Update expired credentials or reconnect after permissions change.

### Use an action

1. Add the required **noCRM.io** action to the workflow.
2. Select a connection when the action requests one.
3. Complete the required fields. Use the reference picker when a value comes from another workflow step.
4. Run the workflow and inspect the action’s output. Check the result before using it in a later step.

### Actions

#### Create Lead

Create an unassigned lead with the essential sales details.

**Inputs**

| Field       | Type     | Required | Description                                                                  |
| ----------- | -------- | -------- | ---------------------------------------------------------------------------- |
| Lead title  | string   | Yes      | A short name for the company, person, or opportunity.                        |
| Description | textarea | Yes      | The useful context a salesperson needs to qualify and follow up on the lead. |
| Tags        | string   | No       | Optional comma-separated labels for organizing the lead.                     |

**Outputs**

| Field   | Type    | Description                           |
| ------- | ------- | ------------------------------------- |
| Lead ID | integer | The identifier of the created lead.   |
| Title   | string  | The title stored on the lead.         |
| Status  | string  | The lead status returned by noCRM.io. |

#### Update Lead Status

Change the business state of one assigned noCRM.io lead.

**Inputs**

| Field         | Type            | Required | Description                                                                                  |
| ------------- | --------------- | -------- | -------------------------------------------------------------------------------------------- |
| Lead          | select (string) | Yes      | The exact lead whose business state will change. Options load from the selected connection.  |
| New status    | select (string) | Yes      | The new business state for the lead. Available values: To do, Standby, Won, Lost, Cancelled. |
| Reminder date | date            | No       | Required for a Standby lead's account-local reminder.                                        |
| Reminder time | string          | No       | Optional account-local time in 15-minute increments for Standby.                             |

**Outputs**

| Field   | Type    | Description                                    |
| ------- | ------- | ---------------------------------------------- |
| Lead ID | integer | The identifier of the updated lead.            |
| Status  | string  | The business status returned after the update. |

#### List Leads

List one bounded page of leads and continue later from the returned offset.

**Inputs**

| Field                    | Type            | Required | Description                                                                                                                                                                                  |
| ------------------------ | --------------- | -------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Maximum results          | integer         | No       | How many leads to return, from 1 to 100. Minimum: 1. Maximum: 100. Default: 50.                                                                                                              |
| Starting offset          | integer         | No       | Where this page starts; use a previous next offset to continue. Minimum: 0. Default: 0.                                                                                                      |
| Status                   | select (string) | No       | Optionally return only leads in one business state. Available values: To do, Standby, Won, Lost, Cancelled.                                                                                  |
| Show advanced options    | boolean         | No       | Show assignment and sorting controls. Default: false.                                                                                                                                        |
| Include unassigned leads | boolean         | No       | Also include leads that do not yet have an owner. Default: false.                                                                                                                            |
| Sort by                  | select (string) | No       | The field used to order the returned page. Available values: ID, Creation date, Last update, Next action, Sales step, Amount, Probability, Probabilized amount, Alphabetically. Default: id. |
| Sort direction           | select (string) | No       | Whether results are sorted in ascending or descending order. Available values: Ascending, Descending. Default: desc.                                                                         |

**Outputs**

| Field       | Type          | Description                                                        |
| ----------- | ------------- | ------------------------------------------------------------------ |
| Leads       | object\_array | The structured lead summaries in this bounded page.                |
| Total count | integer       | The number of matching leads before pagination.                    |
| Next offset | integer       | The offset for the next page, or empty when this is the last page. |

#### Add Comment to Lead

Append one plain-text comment to an exact lead.

**Inputs**

| Field   | Type            | Required | Description                                                                              |
| ------- | --------------- | -------- | ---------------------------------------------------------------------------------------- |
| Lead    | select (string) | Yes      | The exact lead that will receive the comment. Options load from the selected connection. |
| Comment | textarea        | Yes      | The note to append to the lead's activity.                                               |

**Outputs**

| Field      | Type    | Description                            |
| ---------- | ------- | -------------------------------------- |
| Comment ID | integer | The identifier of the created comment. |
| Comment    | string  | The comment text stored by noCRM.io.   |

#### Add Prospect to Prospecting List

Append one ordered prospect row to a selected prospecting list.

**Inputs**

| Field            | Type            | Required | Description                                                                             |
| ---------------- | --------------- | -------- | --------------------------------------------------------------------------------------- |
| Prospecting list | select (string) | Yes      | The list that will receive the new prospect. Options load from the selected connection. |
| Prospect values  | string          | Yes      | One CSV row with values in the selected list's column order.                            |

**Outputs**

| Field       | Type    | Description                                 |
| ----------- | ------- | ------------------------------------------- |
| Prospect ID | integer | The identifier of the added prospect row.   |
| Active      | boolean | Whether the created prospect row is active. |

### Important behavior

Actions that create, update, send, or delete data can change the connected service. Review their inputs before running them. A retry can repeat an operation; consider this when configuring retries for actions that change data.

The catalog lists the fields and capabilities available in the supplied provider definition. Availability can also depend on your deployment and organization’s Feature Access settings.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.stackai.com/integrations/catalog/nocrm.io.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
