Actions26
- Activities Actions
- Project Actions
- Project Member Actions
- Project Document Actions
- Project Data Actions
- Project Work Unit Actions
- Project Indicators Actions
Overview
This node enables managing project documents within a Pulse API-based workflow. Specifically, the "Delete Project Document" operation allows users to remove a document associated with a project by specifying its unique document ID. This is useful in scenarios where outdated or incorrect project documents need to be removed to maintain accurate project records.
Practical examples include:
- Automatically deleting obsolete project files after a milestone is completed.
- Removing confidential documents when a project phase ends.
- Cleaning up test or temporary documents created during project setup.
Properties
| Name | Meaning |
|---|---|
| Document ID * | The unique identifier of the project document to delete |
Output
The output JSON contains the result of the delete operation. Typically, this will confirm whether the deletion was successful or provide relevant status information from the API. The exact structure depends on the API response but generally includes confirmation fields such as success flags or deleted document IDs.
No binary data output is expected for this operation.
Dependencies
- Requires an active connection to the Pulse API via an API key credential configured in n8n.
- The node depends on the Pulse API helper utilities and operation implementations bundled within the node's codebase.
- Proper permissions on the Pulse API are necessary to perform document deletions.
Troubleshooting
Common issues:
- Providing an invalid or non-existent Document ID will likely cause an error.
- Insufficient API permissions can prevent deletion.
- Network or authentication failures may interrupt the operation.
Error messages:
"The operation "deleteProjectDocument" is not supported for resource "projectDocuments"!"— indicates a misconfiguration or unsupported operation; verify the selected operation.- Errors related to missing or invalid Document ID — ensure the Document ID is correctly provided and exists.
- Authentication errors — check that the API key credential is valid and has required scopes.
Resolving these typically involves verifying input parameters, checking API credentials, and ensuring network connectivity.
Links and References
- Pulse API Documentation (replace with actual URL)
- n8n documentation on creating custom nodes
- General best practices for API authentication and error handling in n8n workflows