# Integrating SailPoint with noCRM

noCRM is a lead management (CRM) platform. Each customer has a dedicated organization subdomain and manages users and teams from that tenant. This document covers how to configure a new direct connection between SailPoint and noCRM for Quick Compliance. For a reference to the terminology specific to SailPoint products, refer to [Source and Connector Definitions](<https://documentation.sailpoint.com/saas/help/sources/index.html#source-and-connector-definitions>).

> [!NOTE]
>
> To view the latest features, enhancements, and fixes for all SaaS connectors, refer to the [SaaS Release Notes](<https://community.sailpoint.com/release-notes/saas>) page.

## Supported Features

The noCRM connector supports the following:

### Account Management

- Aggregate Users

### Entitlement Management

- Aggregate Teams

> [!NOTE]
>
> This connector is read-only. It supports test connection, account aggregation, and entitlement aggregation for Quick Compliance. Provisioning, de-provisioning, and write operations are not supported. Team membership on each account is mapped through the multi-valued `team_id` (entitlement) and `team_name` attributes.

> [!IMPORTANT]
>
> Quick Compliance connectors have the following manual aggregation limits within a 24-hour period:
>
> - **Organization Admins**: Limited to 3 manual account or entitlement aggregations per day per source. This limit is cumulative across all admins in the organization.
> - **Regular Users**: Limited to 1 manual account or entitlement aggregation per day per source.
>
> These limits ensure that individual compliance statuses are kept up to date while maintaining continuous compliance monitoring. If you need to run additional aggregations beyond these limits, contact SailPoint Support.

## Prerequisites

Before you configure the noCRM connector, ensure the following requirements are met:

1. Sign in to your noCRM organization.
2. Note your organization subdomain. The API Base URL uses the pattern `https://<your-organization>.nocrm.io/api/v2`. Replace `<your-organization>` with the subdomain you use to sign in. Do not leave a sample tenant URL in the source.
3. Generate an API key from noCRM (**Settings \> Admin / API**). The connector sends this value as the `X-API-KEY` header on every request.
4. Record the following values for connector configuration:

   - **Base URL**
   - **API Token**

> [!NOTE]
>
> - Authentication type is Custom Authentication. Leave Username, Password, and Resource Owner Username blank.
> - Store the API key in the source **API Token** field.

## Required Permissions

Aggregation is read-only. The API key must belong to a user who can list organization users and teams.

- Create the key from an admin user (`is_admin: true`).
- A disabled user (`is_disabled: true`) or a user who has not activated (`has_activated: false`) cannot be used as the integration identity.

For more information about noCRM, refer to the following:

- [noCRM website](<https://www.nocrm.io/>)
- [noCRM API documentation](<https://www.nocrm.io/api>)

> [!NOTE]
>
> The linked document is not maintained by SailPoint and is subject to change without notice.