Actions10
Export → Create
AI-generatedOverview
This node integrates with an OpenRefine server to perform various data wrangling operations. Specifically, the Export - Create operation allows users to export rows from an OpenRefine project using a templated format. This is useful when you want to extract processed data from OpenRefine in a customized text format, for example, exporting cleaned or transformed data for further use in other systems or workflows.
Practical scenarios include:
- Exporting refined datasets after cleaning and transformation.
- Generating custom-formatted reports or data extracts based on project data.
- Automating data extraction from OpenRefine projects within larger automation pipelines.
Properties
| Name | Meaning |
|---|---|
| Server | The URL of the OpenRefine server. Usually defaults to http://127.0.0.1:3333 unless changed. |
| Project ID | The identifier of the OpenRefine project from which to export data. |
Output
The output is an array of JSON objects representing the exported rows from the specified OpenRefine project. Each item corresponds to one row of exported data formatted according to a template constructed dynamically based on the project's column model.
The json output field contains the exported data rows as JSON objects. There is no binary output for this operation.
Dependencies
- Requires access to a running OpenRefine server (default address
http://127.0.0.1:3333). - No explicit API keys or authentication tokens are required by default, but the node fetches a CSRF token from the server to authorize requests.
- The OpenRefine server must support the relevant API endpoints used for exporting data.
Troubleshooting
Common issues:
- Incorrect or unreachable OpenRefine server URL will cause connection errors.
- Invalid or missing Project ID will result in failure to locate the project.
- If the OpenRefine server is not running or accessible, requests will fail.
- CSRF token fetching may fail if the server configuration changes or if the endpoint is unavailable.
Error messages:
- Network errors or timeouts indicate connectivity problems with the OpenRefine server.
- HTTP status codes other than 200 or 302 may indicate permission or request format issues.
- Missing project ID in the redirect location header after export creation may mean the export did not complete successfully.
Resolutions:
- Verify the OpenRefine server URL and ensure it is running.
- Confirm the Project ID is correct and the project exists on the server.
- Check network connectivity and firewall settings.
- Review OpenRefine server logs for more detailed error information.