Description
n8n-nodes-viingx
This is an n8n community node. It lets you connect n8n workflows to viingx systems.
viingx is used to work with structured entity data, files, localizations, workflows, authorization profiles, and webhook-driven events exposed by a viingx installation.
n8n is a fair-code licensed workflow automation platform.
- n8n-nodes-viingx
– Installation
– Operations
– viingx
– Authorization
– Entity
– Entity Localization
– Entity Type
– GraphQL
– Locale
– Response
– Setting
– Share Link
– Workflow
– viingx Trigger
– Credentials
– Compatibility
– Usage
– Working With Entities
– Working With Files
– Working With Localizations
– Trigger Webhooks
– Trigger Responses
– Resources
– Version history
Installation
Follow the installation guide in the n8n community nodes documentation.
The npm package name is:
n8n-nodes-viingx
Operations
viingx
The viingx node supports these resources and operations:
#### Authorization
#### Entity
#### Entity Localization
#### Entity Type
#### GraphQL
#### Locale
#### Response
Use this resource at the end of workflows started by non-subscription triggers to send the expected response payload back to viingx.
#### Setting
#### Share Link
#### Workflow
viingx Trigger
The viingx Trigger node starts a workflow from viingx webhook calls.
Credentials
Create Viingx API credentials in n8n and provide:
/api/v1.0 suffix.The node sends the API key as the x-api-key request header. n8n tests the credentials by calling /api/v1.0/auth/profile on the configured host.
Compatibility
This package uses n8n Nodes API version 1 and n8n-workflow as a peer dependency.
The current development environment uses n8n-workflow 2.19.0 and @n8n/node-cli 0.28.0. There are no known version-specific incompatibilities.
Usage
Working With Entities
Most entity operations require an entity type. The node loads available entity types from the configured viingx instance, and you can also provide an entity type ID with an n8n expression.
For Create Entity, provide:
For Get Entities, the optional Query and Sorting fields use JSON. Example query:
{
"property": "content.payload.name",
"op": "=",
"value": "Test"
}
Example sorting:
[
{
"property": "content.payload.name",
"direction": "asc"
}
]
For media entities, use Create Media Entity From File Data or Update Media Entity From File Data when the incoming n8n item contains binary data. Use Suggest Media Entity Payload From File Data to pre-fill payload fields from the file before creating.
Working With Files
Use Upload File when the incoming n8n item contains binary data. Set Input Binary Field to the binary property name, for example data.
Use Get Entity File to download a viingx file into an n8n binary property. Set Output Binary Property to the property name that should receive the file. The same pattern applies to Get Entity Derivative File, Get Entity Preview File, Get Media Entity Cropped File, and the entity localization file operations.
Working With Localizations
Use Get Entity Localizations to list all locale variants of an entity. Use Create or Update Entity Localization to create or replace a locale-specific content version. Use Get Entity Localization File to download the file attached to a localization.
Trigger Webhooks
Use viingx Trigger when viingx should start an n8n workflow. Choose the matching event type, then configure viingx to send a POST request to the webhook URL shown by n8n for that trigger node.
For Subscription, the trigger responds immediately because it is notification-only. For Action, Quality Gate Check, Workflow Assignee Options, and Workflow State Options, connect the trigger workflow to the viingx node, choose the Response resource, and choose the matching operation.
Trigger Responses
Use the Response resource in the viingx node at the end of workflows started by non-subscription triggers. Choose the operation that matches the trigger event so the node sends the expected response payload.
For asynchronous action triggers, set Action Completion to Asynchronous in viingx Trigger. The trigger returns HTTP 204 automatically, while the workflow continues and can update or finalize the invocation later.
For action responses, choose Send Action Response, then choose the response type:
Send Synchronous Response: Returns the final action result to the invocation request.Update Asynchronous Action Progress: Sends progress to the invocation update endpoint using the invocation ID, token, and host URL from the trigger payload.Finalize Asynchronous Action: Sends the final action result to the invocation finalize endpoint.
