efficy Enterprise CRMInstall

Summary

Updates fields on an existing efficy CRM record by sending an edit context (commit and close) with an update function carrying the supplied field values.

Inputs

• Entity (required) — Efficy entity code of the record, e.g. Comp, Cont, Oppo, Acti, Docu, Proj.
• Entity Key (required) — Primary key of the record to update.
• Fields (JSON) (required) — JSON object of field name → value pairs sent as @data to the update function. Dates in ISO 8601. Invalid JSON raises an error.
• Category — Category tableview to write into (e.g. CONT$EMPLOYEE). If blank, the main tableview (tableview 0) is updated.
• Options > Return Full Response — If enabled, returns the whole API response array (wrapped as { response: [...] }) instead of only the first context result.

Output shape

One output item per input item, containing the first context object of the efficy API response (or the full response when Return Full Response is on).

Efficy-level errors (#error in the response context or function) throw a node error, or with Continue On Fail enabled produce an item with { error: message }. Each request is a single commit-and-close edit, so there is no separate save step. With Server Side Cache enabled in credentials, a Finalize Workflow tool node should end the workflow.

Examples

Example 1: Change the name of a company with key 123.

Entity: Comp; Entity Key: 123; Fields (JSON): {"NAME": "Acme Corp"}

Example 2: Write a value into a category tableview on a contact.

Entity: Cont; Entity Key: 456; Category: CONT$EMPLOYEE; Fields (JSON): {"FIELD": "value"}

Links

• n8n community nodes installation guide