Actions10
Project → Delete
AI-generatedOverview
This node integrates with an OpenRefine server to manage data wrangling projects. Specifically, the Project Delete operation allows users to delete an existing OpenRefine project by specifying its project ID. This is useful for automating cleanup tasks or managing project lifecycle within data workflows.
Typical use cases include:
- Automatically removing obsolete or temporary projects after processing.
- Managing storage and organization on an OpenRefine server by deleting projects no longer needed.
- Integrating OpenRefine project management into larger automated data pipelines.
Properties
| Name | Meaning |
|---|---|
| Server | The URL of the OpenRefine server instance. Defaults to http://127.0.0.1:3333. Change if your server runs elsewhere. |
| Project ID | The unique identifier of the OpenRefine project you want to delete. |
Output
The output JSON contains the response from the OpenRefine server after attempting to delete the specified project. It typically includes:
- Status code of the HTTP request.
- Any message or confirmation returned by the server about the deletion.
- Additional metadata as provided by OpenRefine's API.
No binary data is output by this operation.
Example output structure:
{
"code": 200,
"message": "Project deleted successfully"
}
(Note: Actual fields depend on OpenRefine's API response.)
Dependencies
- Requires access to a running OpenRefine server.
- No special credentials are required beyond the server URL, but the server must be accessible and allow project deletion commands.
- The node fetches a CSRF token from the server before making the delete request, so the server must support this security mechanism.
Troubleshooting
Common issues:
- Incorrect or unreachable server URL will cause connection errors.
- Invalid or non-existent Project ID will result in failure to delete.
- Lack of permissions on the OpenRefine server may prevent deletion.
- Failure to obtain CSRF token due to server configuration or network issues.
Error messages:
- Network errors or timeouts indicate connectivity problems.
- HTTP error codes (e.g., 403 Forbidden) suggest permission issues.
- Errors mentioning missing or invalid CSRF token indicate server-side security enforcement.
Resolutions:
- Verify the OpenRefine server URL and ensure it is reachable.
- Confirm the Project ID exists and is correct.
- Check server permissions and authentication settings.
- Ensure the OpenRefine server supports and correctly responds to CSRF token requests.
Links and References
- OpenRefine Official Website
- OpenRefine API Documentation
- n8n Documentation (for general node usage)