FlowmageDocs

Update person

BetaChanges data

Changes a person in Pipedrive — their name, owner, contact details or labels.

Settings

SettingWhat it is
ConnectionRequiredThe Pipedrive connection the step signs in with.
Person idRequiredtext
Nametext
Owner idThe List users node gives you the id. Leave at 0 for the token's own user.
Organization idnumber
E-mail addressesOne row per address. These rows are typed in, not taken from an earlier node — use the advanced E-mail addresses (whole list) field for that.
Phone numbersOne row per number.
E-mail addresses (whole list)A list of { value, label, primary } objects from an earlier node. When it is filled, the rows above are ignored.
Phone numbers (whole list)Same shape as the e-mail list. When it is filled, the rows above are ignored.
Visible toPipedrive's own visibility number. Leave empty for the company's default.
Label idsComma-separated. Labels are ids in v2, not words.
Custom fieldsKeys are the 40-character field code from the List field definitions node. A postal address, birthday or job title needs contact sync switched on for the company, and Pipedrive refuses them otherwise — reach those with an HTTP Request node.
Technical details
KeyValue
connectiontexta connection id from `requires.connections` (provider `pipedrive`)
personIdtextits `{{ }}` must give a string
nametextits `{{ }}` must give a string
ownerIdnumber, by default 0
orgIdnumber, by default 0
emailslist of {value?: text, label?: "work" or "home" or "mobile" or "other", primary?: "true" or "false"}, by default []
phoneslist of {value?: text, label?: "work" or "home" or "mobile" or "other", primary?: "true" or "false"}, by default []
emailsJsonany JSONits `{{ }}` must give an array
phonesJsonany JSONits `{{ }}` must give an array
visibleTotext
labelIdstext
customFieldsobject (any keys), by default {}

Output

FieldType
personIdstring
personobject
Sample output, and the expression for each field
  • person
    • id1
  • personId"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": {
    "connection": "<connection id>",
    "customFields": {},
    "emails": [],
    "emailsJson": "<e-mail addresses (whole list)>",
    "labelIds": "",
    "name": "",
    "orgId": 0,
    "ownerId": 0,
    "personId": "<person id>",
    "phones": [],
    "visibleTo": ""
  },
  "label": "Update person",
  "type": "pipedrive.updatePerson",
  "version": 1
}