CiviCRMInstall

Summary

Update an existing CiviCRM APIv4 entity record using a legacy raw custom API call with JSON parameters and optional runtime bearer token and base URL override.

Inputs

• Entity (required) — The CiviCRM API4 entity to update, such as Contact, Membership, Group, Activity, CustomValue, etc.
• Action (required) — The CiviCRM API4 action to perform, typically 'update' for this operation, but can be other legacy actions.
• Params (JSON) (required) — Raw JSON string of parameters to pass directly to the CiviCRM API4 call; must be a valid JSON object without trailing commas.
• Runtime Bearer Token (Optional) — Optional JWT token for a specific real user; if provided, it is used exactly as given for authorization, bypassing credentials stored in the node.
• Base URL Override — Optional override for the base URL of the CiviCRM instance to call, useful when sharing an API key across multiple instances.
• Fields — (Displayed for some operations but not relevant here) Fields to set for the entity, not typically used in the legacy update operation.

Output shape

a single JSON object containing the raw CiviCRM API v4 response for the update call.

The response is the raw API4 response JSON, allowing advanced users to work with values and metadata directly. The operation uses direct JSON parameter passing to the specified entity and action, enabling flexible legacy custom API usage. Errors are thrown or returned based on node settings; providing a runtime bearer token enforces permissions for that user without fallback to node credentials.

Links

• n8n community nodes installation guide