CiviCRMInstall

Summary

Update a CiviCRM contact by its ID, applying the supplied fields and any email, phone, or address values. Returns the updated contact with its email, phone, and address records.

Inputs

• ID (required) — Internal CiviCRM contact ID to update.
• Contact Type — Contact type to set: Individual, Organization, or Household. The default is Individual.
• Fields — Add field name/value pairs to update. Values are converted to booleans, numbers, or JSON objects when they match those formats; blank values are skipped. Use names such as first_name or birth_date. email and phone set those contact details; email.*, phone.*, and address.* can set specific subfields. A gender field maps to gender_id, and birth maps to birth_date.
• Email Location Type — Location type used when updating or adding an email record; defaults to Work. A matching location prefix in a field name, such as Home.email, can select another location type.
• Mark Email as Primary — Whether the email record is marked primary; defaults to true.
• Phone Location Type — Location type used when updating or adding a phone record; defaults to Work. A matching location prefix in a field name, such as Mobile.phone, can select another location type.
• Mark Phone as Primary — Whether the phone record is marked primary; defaults to true.
• Address Location Type — Location type used when updating or adding an address record; defaults to Home. A matching location prefix in a field name, such as Billing.address.street_address, can select another location type.
• Mark Address as Primary — Whether the address record is marked primary; defaults to true.
• Runtime Bearer Token (Optional) — Optional per-item JWT, often supplied by expression. When provided, the node uses it for the request without falling back to the credential's API key if the response is empty or errors.
• Base URL Override — Optional per-item CiviCRM site root URL, without /civicrm. If omitted, the credential's Base URL is used; a missing URL scheme is treated as HTTPS.

Output shape

A single contact record per input item, including selected contact fields and chained email, phone, and address records.

For email, phone, and address fields, the operation updates the first existing record matching the contact and selected location type, or creates one if none exists. Ordinary blank field values are skipped, so this operation does not clear fields by passing an empty value. Errors stop execution unless Continue On Fail is enabled; then an item containing an error message is returned.

Links

• n8n community nodes installation guide