LLW CRMInstall

Summary

Selects Document / Update or Create in the LLW CRM node, which has no dedicated runtime branch for documents. Only the optional association settings are declared for it. In the source, the execute method handles updateOrCreate only for the Contact resource, so this operation does not behave as an upsert for documents.

Inputs

• manageAssociations — Boolean, default false. Reveals the association settings. Intended to attach, detach or sync associations after the operation.
• associationOperation — Attach (add without removing), Detach (remove specific) or Sync (replace all). Default is Attach. Shown only when Manage Associations is on.
• associations — JSON object of IDs by type, for example {"companies":[1,2],"contacts":[1,2]}. Shown only when Manage Associations is on.

Output shape

Probably nothing useful. In the source, no branch matches Document with updateOrCreate. responseData stays undefined, so each input item yields one output item whose json is undefined, with pairedItem set.

The properties shown for this operation contain no document fields (title, document type) and no search-by field. The Contact version of Update or Create searches for an existing record, then updates or creates it. Nothing like that is implemented for documents. The only fully working update-or-create path is for Contact. For documents, use the separate Create or Update operations instead. Errors are returned as {error} items when Continue On Fail is enabled.

Examples

Example 1: Upsert a document record (not supported)

Resource Document, Operation Update or Create. No matching execution branch, so no API call is made. Use Create or Update instead.

Links

• n8n community nodes installation guide