Actions13
Overview
The Pickaxe node allows interaction with the Pickaxe API, a platform likely used for managing studios, users, documents, and other related resources. Specifically, the "Delete User" operation under the "Pickaxe" resource enables the deletion of a user from a specified studio by their email address.
This node is beneficial in scenarios where automated user management is required, such as removing access for users who no longer need it or cleaning up user lists programmatically. For example, an organization could automate the removal of users from their Pickaxe studio when employees leave the company or change roles.
Properties
| Name | Meaning |
|---|---|
| Studio | The target studio from which the user will be deleted. Options are dynamically loaded from the Pickaxe API. |
| User Email | The email address of the user to delete from the selected studio. |
Output
The node outputs JSON data representing the result of the delete user operation. This typically includes confirmation of the deletion or any error messages returned by the Pickaxe API. There is no indication that the node outputs binary data.
Dependencies
- Requires an API key credential for authenticating with the Pickaxe API via OAuth2.
- The node makes HTTP requests to
https://api.pickaxe.co/v1endpoints. - The "Studio" property options are dynamically loaded from the Pickaxe API's studios list endpoint.
- Proper configuration of the OAuth2 API credentials within n8n is necessary for successful authentication.
Troubleshooting
Common Issues:
- Invalid or expired API credentials may cause authentication failures.
- Specifying a non-existent studio ID or user email may result in errors or no action.
- Network connectivity issues can prevent communication with the Pickaxe API.
Error Messages:
- Authentication errors typically indicate invalid or missing API tokens; reconfigure credentials accordingly.
- "User not found" or similar errors suggest the provided email does not exist in the selected studio.
- API rate limits or server errors should be handled by retrying after some time or checking API status.
Links and References
- Pickaxe API Documentation (assumed base URL for reference)
- n8n Expressions Documentation (for using expressions in properties)