PipedriveSettings
| Setting | What it is |
|---|---|
| ConnectionRequired | The Pipedrive connection the step signs in with. |
| TitleRequired | text |
| Person id | A lead hangs on a person, an organization or both — fill in at least one of the two. |
| Organization id | number |
| Owner id | The List users node gives you the id. Leave at 0 for the token's own user. |
| Value | number |
| Currency | A three-letter code. Needed as soon as a value is filled in. |
| Expected close date | text |
| Visible to | Pipedrive's own visibility number. Leave empty for the company's default. |
| Label ids | Comma-separated. A lead label's id is a long identifier with dashes. |
| Channel | Pipedrive's own marketing-channel number. Leave at 0 for none. |
| Channel id | text |
Technical details
| Key | Value |
|---|---|
connection | texta connection id from `requires.connections` (provider `pipedrive`) |
title | textits `{{ }}` must give a string |
personId | number, by default 0 |
organizationId | number, by default 0 |
ownerId | number, by default 0 |
amount | number, by default 0 |
currency | text |
expectedCloseDate | textits `{{ }}` must give a string |
visibleTo | text |
labelIds | text |
channel | number, by default 0 |
channelId | text |
Output
| Field | Type |
|---|---|
leadId | string |
lead | object |
Sample output, and the expression for each field
- lead
- id"abc-1"
- leadId"abc-1"
Errors
When a step of this node stops a run, the run page shows a code. Look it up:
Example step
The step as a flow file holds it. Replace each value in <…>.
{
"config": {
"amount": 0,
"channel": 0,
"channelId": "",
"connection": "<connection id>",
"currency": "",
"expectedCloseDate": "",
"labelIds": "",
"organizationId": 0,
"ownerId": 0,
"personId": 0,
"title": "<title>",
"visibleTo": ""
},
"label": "Create lead",
"type": "pipedrive.createLead",
"version": 1
}