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, only records past this date are synced on the first run when no bookmark exists — Deals and Messages filter by updated_at, Chats by last_message_at.

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, Chats, and Messages streams support incremental sync.
- 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, Groups, Origins, Activities, Channel Accounts, and Deal History 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:

Activities

Stream for Clint activities (tasks, calls, meetings, etc.). Uses full table sync. Requires the activities:read scope and the Activities API feature flag on your Clint account.

Field	Type	Description
`id`	String	Activity UUID
`title`	String	Activity title
`type`	String	Activity type (CALL, MAIL, SCHEDULE, TASK, MEETING, WHATSAPP, INSTAGRAM)
`content`	String	Activity description content (may contain HTML)
`template_id`	String	UUID of the activity template that generated this activity, when any
`completed`	Boolean	Whether the activity was completed
`completed_at`	DateTime	Timestamp when the activity was completed
`completed_by`	String	UUID of the user who completed the activity
`due_at`	DateTime	Due date of the activity
`custom`	Boolean	Whether the activity was created manually (not from a stage template)
`no_show`	Boolean	Whether the meeting was marked as no-show
`stage_id`	String	UUID of the pipeline stage the activity belongs to
`created_at`	DateTime	Activity creation timestamp
`updated_at`	DateTime	Last update timestamp
`deal`	Object	Deal the activity belongs to (`id`, `status`, `origin_id`, `stage_id`, `contact`)

Channel Accounts

Stream for Clint channel accounts (WhatsApp/Instagram inboxes). Uses full table sync. Parent stream of Chats.

Field	Type	Description
`id`	String	Channel account UUID
`created_at`	DateTime	Channel account creation timestamp
`name`	String	Display name of the channel account
`type`	String	Channel type (WHATSAPP_OFFICIAL, WHATSAPP, INSTAGRAM)
`status`	String	Connection status (CONNECTED, DISCONNECTED, CANCELLED)
`avatar`	String	Avatar image URL
`identifier`	String	Phone number or channel identifier
`team_id`	String	UUID of the team that owns the channel account
`team`	Object	Team that owns the channel account (`id`, `name`)

Chats

Stream for chats belonging to each channel account. Supports incremental sync via last_message_at.

Field	Type	Description
`id`	String	Chat UUID
`created_at`	DateTime	Chat creation timestamp
`contact_id`	String	UUID of the contact in the conversation
`user_id`	String	UUID of the user assigned to the chat
`status`	String	Chat status (OPEN, CLOSED, WAITING, SNOOZED, REOPENED)
`seen`	Boolean	Whether the chat has been seen
`unread`	Boolean	Whether the chat has unread messages
`replied`	Boolean	Whether the chat has been replied to
`unseen_count`	Integer	Number of unseen messages in the chat
`last_message_at`	DateTime	Timestamp of the last message; used for incremental sync
`last_response_at`	DateTime	Timestamp of the last response
`closed_at`	DateTime	Timestamp when the chat was closed
`last_status_at`	DateTime	Timestamp of the last status change
`first_response_at`	DateTime	Timestamp of the first response
`first_customer_message_at`	DateTime	Timestamp of the first message sent by the customer
`channel_account_id`	String	UUID of the parent channel account
`team_id`	String	UUID of the team handling the chat
`close_window_at`	DateTime	Timestamp when the messaging window closes

Contacts

Stream for Clint contacts (paginated list). Uses full table sync.

Field	Type	Description
`id`	String	Contact UUID
`name`	String	Contact name
`email`	String	Contact e-mail
`username`	String	Username
`ddi`	String	International dialing code (DDI)
`phone`	String	Phone number without DDI
`fullPhone`	String	Full phone with DDI (country code)
`organization.id`	String	Organization ID
`organization.name`	String	Organization name
`organization.fields`	String	Custom organization fields (JSON string)
`created_at`	DateTime	Created at
`updated_at`	DateTime	Last updated at
`tags`	Array	Array of contact tags, each with `id`, `name`, and `color`
`fields`	String	Custom contact fields, stored as a JSON object string

Deal History

Timeline events of each deal (the CRM panel’s History tab). Child stream of Deals.

Field	Type	Description
`id`	String	History event UUID
`deal_id`	String	UUID of the deal the event belongs to
`category`	String	Event type classification (e.g. DEAL_ARCHIVED, DEAL_UNARCHIVED)
`date`	DateTime	Timestamp when the event occurred
`system`	Boolean	Whether the event was generated by the system
`user`	Object	User who performed the action (null for system events), with `id` and `name`
`body`	String	Event payload; shape varies by category, JSON object string
`summary`	String	Human-readable event summary in Portuguese, when available

Deals

Stream for Clint deals. Supports incremental sync via updated_at.

Field	Type	Description
`id`	String	Deal UUID
`origin_id`	String	Origin UUID
`stage_id`	String	Stage UUID
`stage`	String	Deal stage name
`status`	String	Deal status (OPEN, WON, LOST)
`value`	Number	Deal monetary value
`created_at`	DateTime	Created at
`updated_at`	DateTime	Last updated at (any change); used for incremental sync
`updated_stage_at`	DateTime	Last stage update at
`won_at`	DateTime	Won at
`lost_at`	DateTime	Lost at
`won_by`	String	Won by user UUID
`lost_by`	String	Lost by user UUID
`lost_status_id`	String	Lost status UUID
`user`	Object	Deal owner object: `id` (User UUID), `email`, `full_name`
`contact`	Object	Deal contact object: `id`, `name`, `email`, `phone`, `ddi`, `instagram`
`latest_meeting_datetime`	DateTime	Date and time of the latest meeting
`latest_meeting_link`	String	Link to the latest meeting
`fields`	String	Additional deal fields, stored as a JSON object string

Groups

Stream for Clint groups (paginated list). Use for full table sync of groups.

Field	Type	Description
`id`	String	Group UUID
`name`	String	Group name
`archived_at`	DateTime	Archived at
`archived_by`	String	Archived by user UUID

Messages

Stream for chat messages exchanged within each conversation. Child stream of Chats. Supports incremental sync via updated_at.

Field	Type	Description
`id`	String	Message UUID
`created_at`	DateTime	Message creation timestamp
`updated_at`	DateTime	Last update timestamp; used for incremental sync
`chat_id`	String	UUID of the parent chat
`user_id`	String	UUID of the user who sent the message (when sent by a user)
`content`	String	Text content of the message
`type`	String	Message author type (USER, CUSTOMER, EVENT, NOTE)
`sent`	Boolean	Whether the message was sent
`seen`	Boolean	Whether the message was seen
`delivered`	Boolean	Whether the message was delivered
`content_type`	String	Content type (TEXT, IMAGE, AUDIO, VIDEO, DOCUMENT, TEMPLATE)
`content_url`	String	URL of the media content, when any
`external_id`	String	Identifier of the message on the external channel (e.g. WhatsApp)
`content_object`	String	Structured content payload (shape varies by content type), JSON object string
`content_action`	String	Interactive content payload such as template components and buttons, JSON object string
`status`	String	Delivery status (QUEUED, SENT, DELIVERED, READ)
`source`	String	Source that produced the message (e.g. CHAT)

Origins

Stream for Clint origins (paginated list). Use for full table sync of origins.

Field	Type	Description
`id`	String	Origin UUID
`name`	String	Origin name
`group`	Object	Group info for the origin including `id` (Group UUID) and `name`
`stages`	Array	List of stages for the origin, each with `id`, `label`, `order`, and `type`
`archived_at`	DateTime	Archived at
`archived_by`	String	Archived by user UUID

Data Model

The following diagram illustrates the relationships between the core data streams in Clint. Deals reference contacts and origins, and carry their own history and activities; origins belong to groups; chats belong to channel accounts and contain messages.

Implementation Notes

Authentication & API

The connector sends your API token in the api-token HTTP header for requests to https://api.clint.digital/v1 and https://api.clint.digital/v2.
Keep your API token secret and do not share it; it is stored securely in Nekt.
API rate limits (500 requests/minute) are handled automatically by the connector’s built-in backoff mechanism.

Sync behavior

Contacts, Groups, Origins, Activities, and Channel Accounts: No replication key; use FULL_TABLE to sync the current state.
Deals, Chats, and Messages: 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 limits the initial extract (updated_at_start for Deals and Messages, last_message_at_start for Chats).
Deal History: Child stream of Deals with no date filters of its own. Since the Deals stream is incremental, only deals updated since the last run get their history re-fetched; records upsert by primary key.
Messages: Child stream of Chats — only chats returned by the parent sync have their messages fetched.
Activities: Requires the activities:read scope and the Activities API feature flag enabled on your account. If these are missing, the stream is gracefully skipped with a warning.

API errors and skipped records

Persistent API errors: The Clint API may sometimes persistently fail (e.g., returning 500 errors) when attempting to fetch data for records that are in a broken or deleted state (such as certain channel accounts or chats). Instead of crashing the entire sync run, the connector will skip these broken parent records after exhausting retries. A summary of any skipped record IDs is printed in the logs at the end of the run, allowing you to contact Clint support with these IDs for verification.

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.

Skills for agents

Download Clint skills file

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

Documentation

Get started

Context

Activate

Workspace

Resources

Clint as a data source

Configuring Clint as a Source

1. Add account access

2. Select streams

3. Configure data streams

4. Configure data source

5. Check your new source

Streams and Fields

Data Model

Implementation Notes

Authentication & API

Sync behavior

API errors and skipped records

Custom fields

Skills for agents

Download Clint skills file

​Configuring Clint as a Source

​1. Add account access

​2. Select streams

​3. Configure data streams

​4. Configure data source

​5. Check your new source

​Streams and Fields

​Data Model

​Implementation Notes

​Authentication & API

​Sync behavior

​API errors and skipped records

​Custom fields

​Skills for agents

Download Clint skills file

Configuring Clint as a Source

1. Add account access

2. Select streams

3. Configure data streams

4. Configure data source

5. Check your new source

Streams and Fields

Data Model

Implementation Notes

Authentication & API

Sync behavior

API errors and skipped records

Custom fields

Skills for agents