n8n-nodes-delight

Functional Reference

Features and Scope describes the node's functionality, workflows, prerequisites, and documented limitations. Source Review records the files reviewed and verified. This reference serves as the functional foundation for development and the derived website documentation.

This is an n8n community node. It lets you use delight CRM in your n8n workflows.

delight CRM is a business software platform by delight GmbH that provides flexible, all-in-one business solutions including CRM datasets, document management, and event-driven data handling.

n8n is a fair-code licensed workflow automation platform.

Installation
Operations
Credentials
Compatibility
Usage
Resources
Version history

Installation

Follow the installation guide in the n8n community nodes documentation.

After installation:

1. Restart n8n if required by your setup.
2. Create a credential of type delight API (see Credentials).
3. Add the Delight Actions, Delight Polling Trigger, or Delight Webhook Trigger node to a workflow.

Operations

The package includes three node types:

• Delight Actions: read, create, update, and delete CRM records; upload documents to the document center inbox or to specific records.
• Delight Polling Trigger: poll for new or updated records on a schedule.
• Delight Webhook Trigger: receive instant webhook events for record changes.

Delight Actions

Dataset

Dataset operations require selecting a schema. The node loads available schemas and fields dynamically from the delight API. For Get Many, the node supports grouped filter conditions with logical operators (AND / OR), comparisons (=, !=, >, >=, <, <=, LIKE), and optional result limiting.

Document Center Inbox

When uploading an email, the node normalises incoming n8n email payloads and sends them as .eml documents. Supports reply/archive processing, auto-assignment by sender, and configurable metadata (display name, origin, document class, message type).

Attached Document

The Attached Document resource allows you to manage documents linked to individual records within a dataset. Upload documents to attach them to existing records, or download documents already attached to records.

Delight Polling Trigger

n8n checks a selected schema for new or updated records on the configured schedule.

Delight Webhook Trigger

delight pushes events to n8n instantly. The trigger registers an HTTP endpoint with the delight notification handler and cleans it up when the workflow is deactivated.

Credentials

The node uses a credential of type delight API.

Fields

Where to find these values

• REST API URL: provided by your delight administrator; typically your tenant-specific API base URL.
• Username / Password: your delight CRM user account credentials.

Authentication behaviour

The credential logs in to the delight API and stores the returned session key as hidden, sensitive credential data managed by n8n. Subsequent requests send the key in the SESSIONKEY header. A change to the REST API URL, username, or password requires a fresh login before the nodes send another API request.

n8n refreshes the session after HTTP 401 and retries the API request once. There is no additional retry loop or time-based session expiry in this package. Accounts requiring two-factor authentication are not supported.

The credential test performs the same login, including the two-factor authentication check, followed by an authenticated schema query. The account must have permission to query schemas. Existing delightApi credentials and workflow parameter names remain valid.

Compatibility

The authentication implementation targets n8n 2.44.5. Compatibility with n8n 1.x is no longer a target. The package retains n8nNodesApiVersion: 1 and strict mode; that API version is separate from the n8n application version.

Automated tests exercise the authentication modules shipped with n8n 2.44.5, using a simulated credential store and API transport. This does not establish live Delight API or full n8n editor/deployment validation.

Authentication tests

Run npm run test:auth to build and execute the authentication regression tests. The first run downloads integrity-pinned n8n@2.44.5 and its n8n-core@2.44.3 npm archives to the OS temporary directory. Later runs reuse the verified archives. The tests require Node.js, tar, and first-run access to the npm registry; they do not need a Delight account or running n8n server.

Usage

1. Add the Delight Actions node or one of the trigger nodes to a workflow.
2. Select or create a delight API credential.
3. For Delight Actions: choose a resource and operation.
4. Select the relevant dataset schema or document settings.
5. Map values using the field mapper or n8n expressions.

Example: trigger a workflow on new CRM records

1. Delight Webhook Trigger → Event: New Record Created, Schema: select schema
2. Process or route the record data in subsequent nodes.

Example: query and write back to a dataset

1. Any trigger (Schedule, Webhook, etc.)
2. Delight Actions → Dataset → Get Many → apply filters
3. Transform data in n8n
4. Delight Actions → Dataset → Create or Update → write results back

Example: archive incoming emails to the Document Center Inbox

1. Gmail / IMAP Email Trigger / Microsoft Outlook node
2. Delight Actions → Document Center Inbox → Upload Document → Document Class: Email, Message Type: Automatic

The Document Center Inbox operation normalises the email payload from any supported source node automatically.

Example: attach a document to a CRM record

1. File trigger or HTTP request to receive a document
2. Delight Actions → Attached Document → Upload → select schema, provide record ID
3. Map the file content to the upload operation

The attached document will be linked to the specified CRM record.

Resources

• delight GmbH
• delight knowledge base
• n8n community nodes documentation
• n8n documentation

Version history

See CHANGELOG.md