Actions100
- Activity Logs Actions
- Articles Actions
- Asset Layouts Actions
- Asset Passwords Actions
- Assets Actions
- Get Assets
- Get Companies Company Id Assets
- Post Companies Company Id Assets
- Get Companies Company Id Assets Id
- Put Companies Company Id Assets Id
- Delete Companies Company Id Assets Id
- Put Companies Company Id Assets Id Archive
- Put Companies Company Id Assets Id Unarchive
- Put Companies Company Id Assets Id Move Layout
- Cards Actions
- Companies Actions
- Expirations Actions
- Exports Actions
- Folders Actions
- IP Addresses Actions
- Lists Actions
- Magic Dash Actions
- Matchers Actions
- Networks Actions
- Password Folders Actions
- Procedure Tasks Actions
- Procedures Actions
- Public Photos Actions
- Rack Storage Items Actions
- Rack Storages Actions
- Relations Actions
- Uploads Actions
Overview
This node operation deletes a folder identified by its unique ID. It is useful in scenarios where you need to programmatically remove folders from a system or service that organizes data or files into folders. For example, automating cleanup tasks, managing storage by removing obsolete folders, or integrating with external services that require folder deletion as part of a workflow.
Properties
Name | Meaning |
---|---|
Id | ID of the folder to delete (number) |
Output
The node outputs JSON data representing the result of the delete operation. Typically, this would include confirmation of successful deletion or details about any error encountered. The exact structure depends on the API response but generally confirms whether the folder was deleted.
No binary data output is indicated.
Dependencies
- Requires an API key credential for authentication with the external service.
- The node uses a base URL configured via credentials to connect to the service's API.
- Depends on the
@avantguardllc/n8n-openapi-node
package and an OpenAPI specification (openapi.json
) for request building.
Troubleshooting
Common issues:
- Providing an invalid or non-existent folder ID will likely cause an error indicating the folder could not be found.
- Missing or incorrect API credentials will result in authentication errors.
- Network connectivity problems can prevent the node from reaching the API endpoint.
Error messages:
- "Folder not found" or similar indicates the specified ID does not exist.
- Authentication errors suggest checking the API key or token configuration.
- Timeout or connection errors imply network issues or incorrect base URL settings.
Links and References
- Refer to the external service’s API documentation for details on folder management endpoints.
- Consult n8n documentation on how to configure API credentials and use custom nodes.