Actions23
- Activities Actions
- Project Actions
- Project Member Actions
- Project Document Actions
- Project Data Actions
- Project Work Unit Actions
Overview
This node enables managing project documents within a Pulse workflow environment by interacting with the Pulse API. Specifically, the "Delete Project Document" operation allows users to remove a document associated with a project by specifying its unique document ID.
Common scenarios for this node include:
- Automating cleanup of outdated or irrelevant project documents.
- Integrating document lifecycle management into broader project workflows.
- Ensuring compliance by programmatically deleting sensitive documents when no longer needed.
For example, after a project phase completes, you might use this node to delete all temporary documents related to that phase automatically.
Properties
| Name | Meaning |
|---|---|
| Document ID * | The unique identifier of the project document to delete. This is a required string input. |
Output
The node outputs a JSON object representing the result of the delete operation. Typically, this will confirm whether the deletion was successful or provide details about the deleted document. The exact structure depends on the Pulse API response but generally includes status information.
No binary data output is produced by 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 bundled with the node implementation to perform authenticated requests.
- Proper permissions are necessary on the Pulse API side to delete project documents.
Troubleshooting
Common issues:
- Invalid or missing Document ID: Ensure the Document ID provided exists and is correct.
- Insufficient permissions: The API key used must have rights to delete project documents.
- Network or API errors: Check connectivity and Pulse API service status.
Error messages:
"The operation "deleteProjectDocument" is not supported for resource "projectDocuments"!"— This indicates a misconfiguration of the operation or resource; verify that the node parameters are set correctly.- Errors returned from the Pulse API (e.g., "Document not found") will be passed through; check the document ID validity.
- If the node is set to continue on failure, errors will appear in the output JSON under an
errorfield.
Links and References
- Pulse API Documentation (Replace with actual URL if available)
- n8n documentation on Creating Custom Nodes