Where do I find my Pipedrive API key?

In Pipedrive, open your account name in the top right corner, then **Company settings** > **Personal preferences** > **API**. The key is issued per user and per company, so a user who belongs to several Pipedrive companies has a separate key for each of them.

Why does a run fail with the message that the endpoint is not available for the account plan?

Pipedrive gives access to some objects only on certain plans. While the object is not included in your plan, Pipedrive answers the request with an error and the run stops. Pick another report type or upgrade the Pipedrive plan.

How do I turn custom field keys into readable names?

Create a pipeline for the Deal Fields , Person Fields , Organization Fields , or Product Fields report type. Each row carries the field Key and its Name , so you can join it with the keys inside the Custom Fields column.

Can one pipeline export several report types?

No. A pipeline carries one report type, so create a separate pipeline for each Pipedrive object you want in the warehouse.

Does the pipeline load only the records changed since the previous run?

No. Every run reads the object in full and replaces the destination table, so the table always mirrors the Pipedrive account at the time of the run.

Pipedrive

Renta exports 26 Pipedrive objects to your data warehouse: deals, leads, persons, organizations, products, activities, call logs, notes, files, and mail threads. A second group of report types describes the account around those records: pipelines, stages, teams, users, roles, permission sets, and the definitions of every system and custom field.

You choose the fields for each object yourself. Values of custom fields arrive in a single Custom Fields column keyed by the Pipedrive field key, and the field definition report types turn those keys back into names.

Every report type reloads in full on each run, so the destination table repeats the Pipedrive account as it was at the moment the run started.

Authentication

Renta connects to Pipedrive with a personal API key. You copy the key from your Pipedrive settings and paste it into the connection form.

The key carries the permissions of the user it belongs to, so a pipeline loads the records that this user sees in Pipedrive. To export everything the company has, take the key of a user with full access.

Connect Pipedrive source

Follow these steps to add Pipedrive as a source in Renta using your personal API key.

Go to the CatalogStep 1

Navigate to the Connections > Catalog section in the left sidebar.
Open the CRM category and click the Pipedrive card.

Pipedrive card in the CRM category of the Renta catalog

Paste the API keyStep 2

In the API key field, paste your personal Pipedrive API key.

To find it, open your account name in the top right corner of Pipedrive, then Company settings > Personal preferences > API.

Add a new Pipedrive connection page with the API key field

Name the connection and saveStep 3

In the Source name field, specify a name for this data source. It is used exclusively in the Renta interface.
Click Save.

Renta checks the key with Pipedrive before saving the connection, so an invalid or revoked key fails right on this step.

Pipedrive connection setup with the source name field and the Save button

Source createdStep 4

The new source appears in the Sources list with the Active status. You can now use it in pipelines.

Sources list with the new Pipedrive source in the Active status

Create a pipeline

Once the source is connected, create a pipeline to sync your Pipedrive data into your destination.

Create a Pipedrive pipeline

Link your Pipedrive source to a destination and configure the pipeline.

Select Pipedrive as the sourceStep 1

In the left sidebar, click New pipeline. On the Source step, select Pipedrive under Already connected and click Next step.

Select a source step with Pipedrive under Already connected

Select your Pipedrive connectionStep 2

Choose the Pipedrive connection you created earlier and click Next step. The card shows the name of the connection and the date it was added.

Select your Pipedrive connection step with the connection card and its creation date

Select a destinationStep 3

On the Destination step, select your destination (for example, Google BigQuery) and click Next step.

Select a destination step with Google BigQuery under Already connected

Select the destination connectionStep 4

Choose the destination connection you want to load data into and click Next step. The card shows the dataset and project the data will land in.

Select your Google BigQuery connection step with the dataset and project identifiers on the card

Pipeline configuration

On the final step, choose the report, pick its fields, and set the schedule.

Report type

Select which Pipedrive object the pipeline exports. One pipeline loads one report type.

Report type	Description
Activities	Calls, meetings, and tasks with their type, due date, duration, and done state, the record they belong to, and the meeting location broken down into street, locality, and country.
Activity Types	Activity types configured in the account: name, icon, color, and order.
Call Logs	Logged calls: outcome, duration, both phone numbers, start and end time, and the linked activity, person, organization, deal, or lead.
Currencies	Currencies available in the account, with their code, symbol, and decimal precision.
Deal Fields	Definitions of every deal field, system and custom: key, name, field type, and behavior flags.
Deals	Deals with their value, currency, stage, status, and probability. Each row also carries the won, lost, and close times, counters of related activities, files, and emails, the linked person and organization, and custom field values.
Files	Files attached to records: name, size, type, storage location, and the record they belong to.
Filters	Saved filters: type, visibility, owner, and the time each one was last used.
Goals	Company, team, and user goals: expected outcome, period, pipeline, stage, and the progress report.
Lead Sources	The lead sources available in the account.
Leads	Leads with their value and currency, expected close date, source, origin and channel, the linked person and organization, and the archive state.
Legacy Teams	Teams with their manager, member list, and active member count.
Mailbox	Mail threads: subject, snippet, parties, folders, message counts, read and attachment flags, and the linked deal, lead, or project.
Notes	Notes with their content, author, pinned flags, and the record they belong to.
Organization Fields	Definitions of every organization field, system and custom.
Organizations	Organizations with the address broken into components, industry, annual revenue, employee count, owner, and counters of open, won, and lost deals.
Permission Sets	Permission sets: type, app, and number of assignments.
Person Fields	Definitions of every person field, system and custom.
Persons	Persons with their phone numbers, emails, and messenger handles, postal address, job title, owner, linked organization, deal counters, and custom field values.
Pipelines	Pipelines: order, default deal probability, and active flag.
Product Fields	Definitions of every product field, system and custom.
Products	Products with their code, unit, tax, category, billing frequency, and the price list per currency.
Roles	Roles: parent role, level, description, and number of assignments.
Stages	Stages with the pipeline they belong to, their order, deal probability, and rotten-deal settings.
User Settings	Settings of the account the API key belongs to: default currency, fiscal year, duplicate conditions, email sync rules, and notification preferences.
Users	Users with their email, language, time zone, role, admin and active flags, and access rights per feature.

Pipedrive opens some objects only on certain plans. If your plan does not include the object behind the selected report type, the run stops with an error stating that the endpoint is not available for the account plan.

Parameters

Select the Pipedrive fields to include in the destination table.

Each entry shows the field name and, below it, the column name it takes in the destination table. Use the search field to find a parameter by name, or click Select All. The Selected tab shows everything you picked, and the Selected Parameters list below the picker lets you remove a parameter.

The set of available fields depends on the report type. Two of them are worth adding to every pipeline: ID, which identifies the record, and Update Time, which Renta uses to partition the destination table.

Renta flattens the nested objects that Pipedrive returns. The owner, person, and organization of a record arrive as separate columns for the identifier, the name, and the email. An organization address and an activity location arrive twice: as the full string and as separate components such as street, locality, and country.

Fields that hold a list of values load as nested records.

Report type	Fields that load as nested records
Activities	Participants
Legacy Teams	Users
Mailbox	Parties
Persons	Phone, Email, IM
Products	Prices
Users	Access

Fields whose shape depends on the record itself arrive as JSON. These are Custom Fields in the Deals and Persons reports, Label IDs, Attendees and Series in Activities, Expected Outcome and Report in Goals, and the preference objects of User Settings.

Inside Custom Fields, every value is keyed by the Pipedrive field key rather than by the field name. The Deal Fields, Person Fields, Organization Fields, and Product Fields report types carry both the Key and the Name, so load one of them to resolve the keys into names.

Table name

Name the pipeline and the destination table.

Integration name.
The name of the pipeline. It is used exclusively in the Renta interface.
Table name.
The destination table name. You can keep the auto-generated name or enter your own.

Schedule

Choose how often the pipeline runs.

Schedule type	Description
Manual	The pipeline runs only when triggered manually through the interface or via API.
Daily	The pipeline runs once a day at the specified update time.
Interval	The pipeline runs at specified time intervals.
Cron Expression	The pipeline runs on a schedule defined by a cron expression.

For Daily schedules, set the Update time, the exact time each run starts, then click Create pipeline.

Update time selection and the Create pipeline button

Renta also supports API triggers and integration with external orchestrators such as Apache Airflow, Dagster, and Prefect. See the full scheduling documentation for details.

The new pipeline appears in the Pipelines section under the ETL tab, where you can track its runs, progress, and the destination table name.

Pipelines list with the new Pipedrive integration in the Completed status

Sync strategy

Renta synchronizes every Pipedrive report type the same way.

Strategy	Supported report types	Description
Full reload	Activities, Activity Types, Call Logs, Currencies, Deal Fields, Deals, Files, Filters, Goals, Lead Sources, Leads, Legacy Teams, Mailbox, Notes, Organization Fields, Organizations, Permission Sets, Person Fields, Persons, Pipelines, Product Fields, Products, Roles, Stages, User Settings, Users	Renta reads the object in full on every run and replaces the contents of the destination table. The table mirrors the Pipedrive account at the time of the run, and a record that Pipedrive stops returning leaves the table on the next run.

Selecting the Update Time parameter partitions the destination table by the day the record was last changed. Currencies, Goals, Lead Sources, Legacy Teams, Permission Sets, Roles, User Settings, and Users have no update-time field, so their tables stay unpartitioned.

Because every run reads the object in full, the pipeline has no date range or overwrite period settings. Pipedrive counts every request against the daily API budget of your account, so frequent runs on large objects can exhaust that budget.

Frequently asked questions

Ready to get started?

Build your data pipeline today or get a personalized demo. Start free!

Need help?

Get expert support to ensure your project succeeds. We're here to help!

Feature requests?

Help shape our product! Share your ideas for new features and integrations.