> ## Documentation Index
> Fetch the complete documentation index at: https://docs.popsink.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Pipedrive Source

The Pipedrive Source Connector ingests CRM data from Pipedrive — deals, persons, organizations, activities, and more — into Popsink pipelines. It runs on a configurable schedule and performs incremental synchronization, so only records updated since the last run are delivered downstream. Use it to feed sales analytics, forecasting models, and revenue dashboards with up-to-date pipeline data.

## Key Features

* **Incremental synchronization:** the connector tracks each resource's `update_time` cursor across runs and only delivers new or updated records.
* **Selectable resources:** choose which Pipedrive resources to ingest (e.g. `deals`, `persons`, `organizations`, `activities`); available resources are discovered automatically.
* **Scheduled ingestion:** flexible scheduling by minutes, hours, or days, with an immediate first run on creation.

## Prerequisites

* A Pipedrive account with API access.
* A **personal API token**: in Pipedrive, go to **Settings → Personal preferences → API** and copy your token.

## Configuration

| Field              | Required | Description                                                                    |
| ------------------ | -------- | ------------------------------------------------------------------------------ |
| **Company Domain** | Yes      | Your Pipedrive company domain (e.g. `mycompany` for `mycompany.pipedrive.com`) |
| **API Token**      | Yes      | Your personal API token                                                        |
| **Schedule**       | Yes      | Sync frequency — see [Scheduling](#scheduling)                                 |

## Scheduling

API source connectors run on a schedule rather than streaming continuously. A first run is always triggered immediately after the connector is created; subsequent runs depend on the selected mode:

| Mode        | Behavior                                                      | Example                                      |
| ----------- | ------------------------------------------------------------- | -------------------------------------------- |
| **days**    | Runs every N days at 00:00 UTC + offset (in minutes)          | Offset 30 → every day at 00:30 UTC           |
| **hours**   | Runs every N hours at :00 + offset (in minutes)               | Offset 15 → 00:15, 01:15, 02:15, …           |
| **minutes** | Runs every N minutes, anchored on the connector creation time | Created 10:03, interval 10 → 10:13, 10:23, … |