Actions8
- Table Actions
- Endpoint Actions
- Pipeline Actions
- Query Actions
- Script Actions
Overview
The node allows users to trigger a pipeline run on a selected server within the UbuntuFabric platform. It supports two types of synchronization: a standard sync and a full resync. This node is useful for automating data synchronization workflows, ensuring that data pipelines are executed on demand or as part of larger automation processes.
Typical use cases include:
- Starting a data sync pipeline after new data ingestion.
- Triggering a full resynchronization when data integrity needs to be restored.
- Automating pipeline runs based on external events or schedules.
Properties
| Name | Meaning |
|---|---|
| Server Name or ID | Selects the target server where the pipeline will be run. Can be chosen from a list or specified by ID. |
| Sync Type | Defines the type of synchronization to perform: "Sync" (incremental sync) or "Full Sync" (complete resync). |
Output
The node outputs JSON data representing the response from the pipeline run request. This typically includes status information about the triggered pipeline execution, such as confirmation of start, any identifiers related to the run, or error messages if the run could not be started.
No binary data output is indicated.
Dependencies
- Requires an API key credential to authenticate with the UbuntuFabric platform.
- The node makes HTTP POST requests to the endpoint
api/servers/{pipelineId}/{syncType}on the base URLhttps://app.ubuntufabric.io/. - Proper configuration of the API authentication credential in n8n is necessary.
Troubleshooting
Common issues:
- Invalid or missing server ID: Ensure the server ID or name is correctly selected or provided.
- Authentication failures: Verify that the API key credential is valid and has sufficient permissions.
- Network connectivity problems: Confirm that n8n can reach
https://app.ubuntufabric.io/.
Error messages:
- Unauthorized or 401 errors indicate invalid credentials.
- 404 errors may mean the specified server or pipeline does not exist.
- 400 errors could result from invalid parameters, such as unsupported sync types.
Resolving these usually involves checking input values, verifying credentials, and ensuring the target server exists and is accessible.
Links and References
- UbuntuFabric API Documentation (assumed general reference)
- n8n Expressions Documentation – for using expressions in property fields