Actions13
Overview
The Pickaxe node allows users to interact with the Pickaxe API, specifically managing resources such as studios and documents within those studios. The "Delete Document" operation enables users to delete a specific document from a chosen studio. This is useful in scenarios where documents need to be programmatically removed based on workflow conditions, such as cleaning up outdated or irrelevant data.
Practical examples include:
- Automatically deleting documents after processing their content.
- Removing test or temporary documents created during automated workflows.
- Managing document lifecycle by deleting documents that no longer meet certain criteria.
Properties
| Name | Meaning |
|---|---|
| Studio | Select the studio from which the document will be deleted. Options are dynamically loaded from your Pickaxe account's studios. You can also specify an ID using an expression. |
| Documents | Select the document to delete from the chosen studio. Options are dynamically loaded based on the selected studio. You can also specify an ID using an expression. |
Output
The node outputs JSON data representing the result of the delete operation. Typically, this would include confirmation of deletion or any relevant metadata returned by the Pickaxe API. The exact structure depends on the API response but generally confirms whether the document was successfully deleted.
There is no indication that the node outputs binary data.
Dependencies
- Requires an active connection to the Pickaxe API via OAuth2 authentication.
- Needs configuration of an API authentication token credential for Pickaxe.
- The node makes HTTP requests to
https://api.pickaxe.co/v1endpoints. - Dynamic loading of options (studios and documents) depends on successful API calls to Pickaxe.
Troubleshooting
Common issues:
- Failure to authenticate due to invalid or expired API credentials.
- Selecting a studio or document that does not exist or has been deleted.
- Network connectivity problems preventing API calls.
Error messages and resolutions:
- Authentication errors: Verify that the API key or OAuth2 token is correctly configured and has not expired.
- Resource not found: Ensure the selected studio and document IDs are valid and currently exist in Pickaxe.
- API rate limits or server errors: Retry after some time or check Pickaxe service status.
If dynamic option loading fails, verify that the credentials are correct and that the user has access to the requested studios and documents.
Links and References
- Pickaxe API Documentation (general reference for API endpoints)
- n8n Expressions Documentation (for specifying IDs dynamically)