Actions8
- Endpoint Actions
- Pipeline Actions
- Query Actions
- Script Actions
- Table Actions
Overview
This node integrates with the Peliqan platform to run data synchronization pipelines. Specifically, the "Pipeline" resource with the "Run" operation allows users to start a sync process on a selected server or pipeline. This is useful for automating data sync tasks, ensuring that data between systems stays up-to-date.
Typical use cases include:
- Triggering incremental or full data synchronizations on demand.
- Automating data refresh workflows in ETL (Extract, Transform, Load) processes.
- Integrating Peliqan's sync capabilities into broader automation scenarios within n8n.
For example, a user might configure this node to run a "Full Sync" on a specific pipeline after updating source data, ensuring all downstream systems receive the latest information.
Properties
| Name | Meaning |
|---|---|
| Server Name or ID | Selects the target server or pipeline to start the sync on. Can be chosen from a list or specified via an expression. |
| Sync Type | Defines the type of synchronization to perform. Options are: "Sync" (incremental sync) and "Full Sync" (complete resync). |
Output
The node outputs JSON data representing the result of the pipeline run request. This typically includes status information about the sync operation initiated on the selected pipeline/server.
No binary data output is indicated by the code.
Dependencies
- Requires an API key credential for authenticating with the Peliqan service.
- The node communicates with the Peliqan API at
https://app.eu.peliqan.io/. - The node depends on internal methods and resources bundled within the node package to load options and route requests.
Troubleshooting
Common issues:
- Invalid or missing pipeline ID: Ensure the "Server Name or ID" property is correctly set and corresponds to an existing pipeline.
- Authentication errors: Verify that the API key credential is valid and has sufficient permissions.
- Network or API endpoint errors: Check connectivity to the Peliqan API URL and confirm the service is operational.
Error messages:
- Errors related to missing required parameters will occur if "Server Name or ID" or "Sync Type" are not provided.
- API response errors may indicate permission issues or invalid pipeline IDs; reviewing the API key and input values can resolve these.
Links and References
- Peliqan API Documentation (general reference to the base URL)
- n8n Expressions Documentation (for using expressions in property fields)