# Pipedrive - Workflow node | Docs - nodulz

Source: https://nodulz.com/docs/nodes/pipedrive

Language: en

Manage CRM contacts, leads, companies and opportunities.

## Usage and specifics

Choose the CRM credential, account URL, object and action. Reading, updating and deleting require the record ID. Guided fields override matching advanced JSON keys. Responses retain provider envelopes and pagination; renew OAuth tokens in credentials.

Technical type : `pipedrive`. Runtime : `nodulz`.

## Credentials and prerequisites

- [Pipedrive](/docs/credentials) (`integration` / `pipedrive`). Pipedrive personal API token from Personal preferences > API.

Create credentials in your nodulz instance’s Credentials area, then select them on the node. Availability depends on ownership and sharing. See the [credentials guide](/docs/credentials) for access and rotation.

## Parameters

Names below are technical keys. Defaults are not a ready-to-run configuration: complete fields required by your operation. Paths containing [] describe list items; some fields depend on the selected mode.

| Parameter | Type | Default | Values / limits |
| --- | --- | --- | --- |
| `credentialId` | `string` | `""` | - |
| `operation` | `enum` | `"list"` | `list`, `get`, `create`, `update`, `delete` |
| `host` | `string` | `""` | - |
| `resource` | `string` | `"persons"` | - |
| `resourceId` | `string` | `""` | - |
| `viewId` | `string` | `""` | - |
| `fields` | `array` | `[]` | - |
| `fields[].name` | `string` | - | - |
| `fields[].value` | `string` | - | - |
| `data` | `string` | `"{}"` | - |
| `query` | `string` | `"{}"` | - |

## Configuration help

| Setting | Purpose and guidance |
| --- | --- |
| `host`<br>CRM account URL | HTTPS origin only, without a path or parameters. See the example below. Official provider domains are supported. |
| `resource`<br>CRM object | Exact API object or table name. Salesforce, Zoho and Dynamics also accept custom names. Changing the object resets fields and parameters. |
| `viewId`<br>View ID | Required for Freshsales lists. Find views with GET /crm/sales/api/contacts/filters, replacing contacts with the selected resource. Enter the numeric view ID. |

## Initial configuration

Initial catalog configuration example, to adapt before running. Keep secrets in credentials.

```json
{
  "credentialId": "",
  "operation": "list",
  "host": "",
  "resource": "persons",
  "resourceId": "",
  "viewId": "",
  "fields": [],
  "data": "{}",
  "query": "{}"
}
```

## Verification

Test with representative data. Check node output in the inspector and logs, then use editor mapping for downstream fields. A trigger test with a simulated payload does not validate external service delivery.

See also : [Expressions and data](/docs/expressions), [Executions](/docs/executions), [Node catalog](/docs/nodes).

## Explore further

- [Features - nodulz](https://nodulz.com/product/overview)
- [Node catalog - nodulz](https://nodulz.com/product/catalog)
- [MCP server - nodulz](https://nodulz.com/product/mcp)
- [Pricing - nodulz](https://nodulz.com/pricing)
- [Use cases and workflow automation - nodulz](https://nodulz.com/use-cases)
- [Choose what your workflows can do. - nodulz](https://nodulz.com/compare)
- [Documentation - nodulz](https://nodulz.com/docs)