Skip to main content
NectarCRM is a Brazilian CRM platform designed for B2B sales teams. It provides tools for managing contacts, opportunities, qualifications, tasks, appointments, and sales pipelines, helping teams track their sales processes from prospecting to closing.

​
Configuring NectarCRM as a Source

In the Sources tab, click on the “Add source” button located on the top right of your screen. Then, select the NectarCRM option from the list of connectors. Click Next and you’ll be prompted to add your access.

​
1. Add account access

You’ll need to provide your NectarCRM API access token. To find it, go to Settings > Integrations > Public Token in your NectarCRM account. The following configurations are available:
  • API Key: Your NectarCRM API access token (required).
  • Start Date: The earliest date from which records will be synced for incremental streams.
Once you’re done, click Next.

​
2. Select streams

Choose which data streams you want to sync. For faster extractions, select only the streams that are relevant to your analysis. You can select entire groups of streams or pick specific ones. Select the streams and click Next.

​
3. Configure data streams

Customize how you want your data to appear in your catalog. Select the desired layer where the data will be placed, a folder to organize it inside the layer, a name for each table, and the type of sync.
  • Layer: choose between the existing layers on your catalog.
  • Folder: a folder can be created inside the selected layer to group all tables.
  • Table name: a name is suggested, but feel free to customize it. You can add a prefix to all tables at once.
  • Sync Type: you can choose between INCREMENTAL and FULL_TABLE.
    • Incremental: only new or updated data is fetched each run.
    • Full table: the current state of the data is fetched each run.
Once you are done configuring, click Next.

​
4. Configure data source

Describe your data source for easy identification within your organization, not exceeding 140 characters. To define your Trigger, consider how often you want data to be extracted from this source. Once you are ready, click Next to finalize the setup.

​
5. Check your new source

You can view your new source on the Sources page. If needed, manually trigger the source extraction by clicking on the arrow button. Once executed, your data will appear in your Catalog.
For you to be able to see it on your Catalog, you need at least one successful source run.

​
Streams and Fields

​
Available streams

The table below lists every stream, its slug (the exact identifier to pass when creating the source via API) and a short description.
Fields typed as String (JSON) carry nested objects or arrays of objects returned by the API, serialized as JSON strings. This keeps the warehouse schema stable while preserving all data returned by NectarCRM.

​
Fields by stream

Below you’ll find all available data streams from NectarCRM and their corresponding fields:

​
Implementation Notes

​
Tasks Stream Partitioning

The NectarCRM API silently filters the /tarefas/ (Tasks) endpoint to a single status by default (0 = Aberta) and does not accept a comma-separated list of statuses. To guarantee that all tasks are synced regardless of their status, the connector uses partition-aware logic. It sweeps the API individually for each task status:
  • 0 (Aberta)
  • 1 (Concluída)
  • 2 (Cancelada)
  • 3 (Em execução)
Since every task has exactly one status, these partitioned requests return disjoint sets of IDs that merge cleanly into a single table on Nekt. Additionally, each status partition maintains its own independent incremental state bookmark to ensure accurate state management across all statuses during incremental syncs.

​
Opportunities Status Coverage

The /oportunidades/ endpoint defaults to returning in-progress opportunities only. The connector explicitly requests all statuses (status=1,2,3,4) so that won, lost, and extended opportunities are also synced.

​
Skills for agents

Download NectarCRM skills file

NectarCRM connector documentation as plain markdown, for use in AI agent contexts.