Actions10
Project Metadata → Update
AI-generatedOverview
This node integrates with OpenRefine, an open-source desktop application for data wrangling, allowing users to automate and manage OpenRefine projects and metadata via n8n workflows. Specifically, the Project Metadata - Update operation enables updating metadata associated with OpenRefine projects.
Use cases include:
- Automating updates to project metadata in OpenRefine as part of a larger data processing workflow.
- Synchronizing project metadata changes triggered by external events or systems.
- Managing project tags or other metadata attributes programmatically without manual intervention.
For example, you might update metadata fields after cleaning or transforming data in OpenRefine, ensuring that project information stays current and consistent.
Properties
| Name | Meaning |
|---|---|
| Server | The URL of the OpenRefine server. Defaults to http://127.0.0.1:3333. Change if your server runs elsewhere. |
Output
The node outputs JSON data representing the response from the OpenRefine server after attempting to update project metadata. This typically includes status codes, messages, and any updated metadata details returned by the API.
The output is structured as an array of JSON objects, each corresponding to an input item processed. For the "Update" operation on "Project Metadata," the exact structure depends on the OpenRefine API response but generally confirms success or failure of the update request.
No binary data output is produced by this operation.
Dependencies
- Requires access to a running OpenRefine server reachable at the specified
ServerURL. - The node internally fetches a CSRF token from the OpenRefine server to authorize requests.
- No additional credentials are required beyond the server address.
- Ensure network connectivity and that the OpenRefine server's API endpoints are accessible from the n8n instance.
Troubleshooting
- CSRF Token Fetch Failure: If the node cannot retrieve the CSRF token, it will fail. Verify the OpenRefine server is running and accessible at the provided URL.
- Invalid Server URL: Using an incorrect or unreachable server address will cause connection errors. Confirm the server URL and port.
- Permission Issues: If the OpenRefine server requires authentication or has IP restrictions, ensure n8n has proper access.
- Malformed Input Data: Providing invalid JSON or improperly formatted parameters may cause API errors. Validate inputs before execution.
- Unexpected API Responses: If OpenRefine changes its API or response format, the node may not handle responses correctly. Check OpenRefine version compatibility.
Common error messages usually relate to network issues, authorization failures, or invalid parameters. Resolving these involves verifying server availability, input correctness, and network permissions.