Skip to main content
Clint is a CRM and sales platform that helps teams manage contacts, deals, and groups. The connector extracts data from the Clint API (api.clint.digital) so you can centralize your commercial pipeline and contact data in your Lakehouse.

​
Configuring Clint as a Source

In the Sources tab, click on the “Add source” button located on the top right of your screen. Then, select the Clint 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 Clint API token so Nekt can access your data. The token is sent in the api-token header for all API requests. The following configurations are available:
  • API Token: Your Clint API token. This is required and is sent in the api-token header. Obtain it from your Clint account or API settings.
  • Start Date: (Optional) For streams that support incremental sync (e.g. Deals), only records with updated_at greater than or equal to this date are synced on the first run when no bookmark exists.
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.
Tip: The stream can be found more easily by typing its name.
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 (which will effectively contain the fetched data) and the type of sync.
  • Layer: choose between the existing layers on your catalog. This is where you will find your new extracted tables as the extraction runs successfully.
  • Folder: a folder can be created inside the selected layer to group all tables being created from this new data source.
  • Table name: we suggest a name, but feel free to customize it. You have the option to add a prefix to all tables at once and make this process faster!
  • Sync Type: you can choose between INCREMENTAL and FULL_TABLE.
    • Incremental: every time the extraction happens, we’ll get only the new data - which is good if, for example, you want to keep every record ever fetched. The Deals stream supports incremental sync based on updated_at.
    • Full table: every time the extraction happens, we’ll get the current state of the data - which is good if, for example, you don’t want to have deleted data in your catalog. Contacts and Groups are typically synced as full table.
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. This decision usually depends on how frequently you need the new table data updated (every day, once a week, or only at specific times). Optionally, you can define some additional settings:
  • Configure Delta Log Retention and determine for how long we should store old states of this table as it gets updated. Read more about this resource here.
  • Determine when to execute an Additional Full Sync. This will complement the incremental data extractions, ensuring that your data is completely synchronized with your source every once in a while.
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

Below you’ll find all available data streams from Clint and their corresponding fields:
Stream for Clint contacts (paginated list). Uses full table sync.Key Fields:
  • id - Contact UUID
  • name - Contact name
  • email - Contact e-mail
  • username - Username
  • ddi - International dialing code (DDI)
  • phone - Phone number without DDI
  • fullPhone - Full phone with DDI (country code)
Organization:
  • organization.id - Organization ID
  • organization.name - Organization name
  • organization.fields - Custom organization fields (JSON string)
Timestamps:
  • created_at - Created at
  • updated_at - Last updated at
Tags & Custom Fields:
  • tags - Array of contact tags, each with id, name, and color
  • fields - Custom contact fields, stored as a JSON object string
Stream for Clint deals. Supports incremental sync via updated_at.Key Fields:
  • id - Deal UUID
  • origin_id - Origin UUID
  • stage_id - Stage UUID
  • stage - Deal stage name
  • status - Deal status (OPEN, WON, LOST)
  • value - Deal monetary value
Timestamps:
  • created_at - Created at
  • updated_at - Last updated at (any change); used for incremental sync
  • updated_stage_at - Last stage update at
  • won_at - Won at
  • lost_at - Lost at
Ownership & Outcome:
  • won_by - Won by user UUID
  • lost_by - Lost by user UUID
  • lost_status_id - Lost status UUID
Related Entities:
  • user - Deal owner object: id (User UUID), email, full_name
  • contact - Deal contact object: id, name, email, phone, ddi, instagram
Meetings:
  • latest_meeting_datetime - Date and time of the latest meeting
  • latest_meeting_link - Link to the latest meeting
Custom Data:
  • fields - Additional deal fields, stored as a JSON object string
Stream for Clint groups (paginated list). Use for full table sync of groups.Key Fields:
  • id - Group UUID
  • name - Group name
Archival:
  • archived_at - Archived at
  • archived_by - Archived by user UUID

​
Data Model

The following diagram illustrates the relationships between the core data streams in Clint. Deals reference contacts and are owned by users; groups are independent entities.

​
Implementation Notes

​
Authentication

  • The connector sends your API token in the api-token HTTP header for every request to https://api.clint.digital/v1.
  • Keep your API token secret and do not share it; it is stored securely in Nekt.

​
Sync behavior

  • Contacts and Groups: No replication key; use FULL_TABLE to sync the current state.
  • Deals: Replication key is updated_at. Use INCREMENTAL to fetch only records changed since the last run. On the first run (or when no bookmark exists), the optional Start Date config is used as updated_at_start so you can limit the initial extract to a date range.

​
Custom fields

  • Contacts and Deals can have custom fields (key-value data). The tap serializes these as JSON strings in the fields column for compatibility with a fixed schema since fields can be dynamic.