NoCRM

noCRM.io is a lead management tool built for sales teams to track prospects, organize follow-ups, and move leads through the sales pipeline. The Nexla connector uses the noCRM.io REST API to ingest records such as leads, activities, pipelines, and teams, and to create or update leads, comments, activities, and prospecting lists. Requests are authenticated with an API key sent in the X-API-KEY header.

Power end-to-end data operations for your NoCRM API with Nexla. Our bi-directional NoCRM connector is purpose-built for NoCRM, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to NoCRM or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your NoCRM workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

• Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
• Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
• API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
• Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

Prerequisites

Before creating a NoCRM credential, you need a noCRM.io account and an API key. noCRM.io authenticates all API requests with an API key sent in the X-API-KEY request header, and requests are made against your account's own subdomain.

To obtain your NoCRM credentials, follow these steps:

1. Sign in to your noCRM.io account with an administrator user.

2. Open the Admin Panel, then navigate to Integrations > API > API Keys.

3. Click Create an API Key to generate a new key. Give the key a descriptive name so you can identify the integration later.

4. Copy the API key immediately. noCRM.io displays the key only once at the moment of creation. If you lose it, you will need to deactivate the old key and generate a new one.

5. Note your account base URL. noCRM.io API requests use your account subdomain in the form https://yourcompany.nocrm.io/api/v2, where yourcompany is your account name.

Treat the API key like an administrator password and keep it confidential. You can deactivate a key at any time from the Admin Panel and generate a replacement. Note that noCRM.io limits API usage to 2,000 requests per day per account. For more information, see the noCRM.io API Reference.

Authenticate

Credentials required

Field	Required	Secret	Description
API Key	Yes	Yes	API key.
Base URL	Yes	No	API base URL, e.g. https://yourcompany.nocrm.io/api/v2

Create a credential in Nexla

1. After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

2. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

3. Enter your noCRM.io API key in the API Key field. This is the key you generated in the Admin Panel during Prerequisites. It is sent in the X-API-KEY header for all API requests and must be kept confidential.

4. Enter your account base URL in the Base URL field, in the form https://yourcompany.nocrm.io/api/v2.

5. Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.

Use as a data source

To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the NoCRM connector tile, then select the credential that will be used to connect to the noCRM.io account, and click Next; or, create a new NoCRM credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common noCRM.io endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.

[Rest API] List Users

Retrieve users from your noCRM.io account. Use this template to bring in the list of user accounts, which can be joined with lead, activity, and team data for reporting.

For details about the response fields returned by this endpoint, see the noCRM.io API Reference.

[Rest API] List Clients Folders

Retrieve clients folders from your noCRM.io account. Use this template to ingest the client records organized in your account.

For details about the response fields returned by this endpoint, see the noCRM.io API Reference.

[Rest API] List Teams

Retrieve teams from your noCRM.io account. Use this template to ingest the teams configured in your account for organizing users and leads.

For details about the response fields returned by this endpoint, see the noCRM.io API Reference.

[Rest API] List Webhooks

Retrieve webhooks configured in your noCRM.io account. Use this template to ingest the webhook subscriptions registered for your account.

For details about the response fields returned by this endpoint, see the noCRM.io API Reference.

[Rest API] List Webhook Events

Retrieve webhook events from your noCRM.io account. Use this template to ingest the event types that can trigger your configured webhooks.

For details about the response fields returned by this endpoint, see the noCRM.io API Reference.

[Rest API] List Steps

Retrieve steps from your noCRM.io account. Use this template to ingest the sales steps that define stages within your pipelines.

For details about the response fields returned by this endpoint, see the noCRM.io API Reference.

[Rest API] List Pipelines

Retrieve pipelines from your noCRM.io account. Use this template to ingest the sales pipelines used to organize and progress leads.

For details about the response fields returned by this endpoint, see the noCRM.io API Reference.

[Rest API] List Categories

Retrieve categories from your noCRM.io account. Use this template to ingest the categories used to classify leads and other records.

For details about the response fields returned by this endpoint, see the noCRM.io API Reference.

[Rest API] List Predefined Tags

Retrieve predefined tags from your noCRM.io account. Use this template to ingest the tags that can be applied to leads for filtering and segmentation.

For details about the response fields returned by this endpoint, see the noCRM.io API Reference.

[Rest API] List Fields

Retrieve fields from your noCRM.io account. Use this template to ingest the custom and standard field definitions configured for your leads.

For details about the response fields returned by this endpoint, see the noCRM.io API Reference.

[Rest API] List Leads

Retrieve leads from your noCRM.io account. Use this template to ingest lead records for analysis, reporting, or downstream integration.

• This endpoint is paginated. Nexla automatically pages through the results, requesting subsequent pages until no further records are returned.

For details about the response fields returned by this endpoint, see the noCRM.io API Reference.

[Rest API] List Follow Ups

Retrieve follow-ups from your noCRM.io account. Use this template to ingest the follow-up actions scheduled against your leads.

For details about the response fields returned by this endpoint, see the noCRM.io API Reference.

[Rest API] List Activities

Retrieve activities from your noCRM.io account. Use this template to ingest the logged activities, such as calls and notes, recorded against your leads.

For details about the response fields returned by this endpoint, see the noCRM.io API Reference.

[Rest API] List Prospecting Lists

Retrieve prospecting lists (spreadsheets) from your noCRM.io account. Use this template to ingest the prospecting lists used to organize and qualify prospects.

• This endpoint is paginated. Nexla automatically pages through the results, requesting subsequent pages until no further records are returned.

For details about the response fields returned by this endpoint, see the noCRM.io API Reference.

Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.

Manual configuration

NoCRM data sources can also be manually configured to ingest data from any valid noCRM.io API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.

Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new NoCRM data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.

Use as a destination

Click the + icon on the Nexset that will be sent to the NoCRM destination, and select the Send to Destination option from the menu. Select the NoCRM connector from the list of available destination connectors, then select the credential that will be used to connect to the noCRM.io account, and click Next; or, create a new NoCRM credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common noCRM.io endpoints. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.

[Rest API] Create Lead

Create a new lead in noCRM.io using records from a Nexset. Use this template to automatically add leads to your account based on data from your Nexla flows.

• Each record from your Nexset is sent as a JSON request body to create a new lead. Ensure the record fields match the structure expected by the noCRM.io API for lead creation.

For details about the request body and available lead fields, see the noCRM.io API Reference.

[Rest API] Update Lead

Update an existing lead by ID in noCRM.io using records from a Nexset. Use this template to keep lead records in noCRM.io in sync with data from your Nexla flows.

• This endpoint requires a Lead ID parameter identifying the lead to update. Each record from your Nexset is sent as a JSON request body containing the updated field values.

For details about the request body and available lead fields, see the noCRM.io API Reference.

[Rest API] Create Lead Comment

Add a comment to a lead in noCRM.io using records from a Nexset. Use this template to append notes or comments to existing leads based on data from your Nexla flows.

• This endpoint requires a Lead ID parameter identifying the lead to comment on. Each record from your Nexset is sent as a JSON request body containing the comment content.

For details about the request body and available comment fields, see the noCRM.io API Reference.

[Rest API] Create Prospecting List

Create a new prospecting list in noCRM.io using records from a Nexset. Use this template to automatically create prospecting lists based on data from your Nexla flows.

• Each record from your Nexset is sent as a JSON request body to create a new prospecting list. Ensure the record fields match the structure expected by the noCRM.io API.

For details about the request body and available fields, see the noCRM.io API Reference.

[Rest API] Create Activity

Log an activity, such as a call, on a lead in noCRM.io using records from a Nexset. Use this template to automatically record activities against existing leads based on data from your Nexla flows.

• This endpoint requires a Lead ID parameter identifying the lead to log the activity on. Each record from your Nexset is sent as a JSON request body containing the activity details.

For details about the request body and available activity fields, see the noCRM.io API Reference.

Manual configuration

NoCRM destinations can also be manually configured to send data to any valid noCRM.io API endpoint. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.

noCRM.io APIs expect JSON format for create and update operations. For update operations, include the ID of the object to be updated in the endpoint URL.

Save & activate

Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To send the data to the configured noCRM.io endpoint, open the destination resource menu, and select Activate.

The Nexset data will not be sent to the noCRM.io endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.