Actions10
AsyncProcesses → Get
AI-generatedOverview
This node integrates with OpenRefine, an open-source desktop application for data wrangling. Specifically, the AsyncProcesses: Get operation retrieves information about asynchronous processes running within a specified OpenRefine project. This is useful for monitoring long-running tasks or background operations in OpenRefine projects.
Typical use cases include:
- Checking the status of data transformation or import/export jobs that run asynchronously.
- Monitoring progress or completion of batch operations applied to a project.
- Integrating OpenRefine workflows into automated pipelines where process state needs to be tracked.
For example, after triggering a complex data cleaning operation in OpenRefine, you can use this node to query the current async processes and determine if the operation has finished or is still running.
Properties
| Name | Meaning |
|---|---|
| Server | The URL of the OpenRefine server. Default is http://127.0.0.1:3333. Change only if your server differs. |
| Project ID | The unique identifier of the OpenRefine project whose async processes you want to retrieve. |
Output
The output is a JSON array where each item represents an asynchronous process related to the specified project. Each JSON object contains details about a single async process as returned by the OpenRefine API. Typical fields may include process IDs, status, progress, and other metadata describing the async task.
No binary data is output by this operation.
Example output snippet (simplified):
[
{
"id": "process-id-123",
"status": "running",
"progress": 50,
"description": "Applying transformations"
},
{
"id": "process-id-456",
"status": "completed",
"progress": 100,
"description": "Data export"
}
]
Dependencies
- Requires access to a running OpenRefine server.
- The node fetches a CSRF token from the OpenRefine server before making requests.
- No special credentials are required beyond the server URL, but the OpenRefine instance must be accessible from n8n.
- The node uses HTTP requests to interact with OpenRefine's REST API endpoints.
Troubleshooting
- Connection errors: Ensure the OpenRefine server URL is correct and reachable from the n8n environment.
- CSRF token fetch failure: If the node cannot retrieve the CSRF token, verify that the OpenRefine server is running and not blocking requests.
- Invalid Project ID: If the project ID does not exist or is incorrect, the API will return an error or empty results. Double-check the project ID.
- Permission issues: If OpenRefine is secured behind authentication or firewall rules, ensure n8n has proper access.
- Unexpected response format: If OpenRefine changes its API, the node might fail parsing responses. Check OpenRefine version compatibility.