Pulse Workflow icon

Pulse Workflow

Workflow actions from Pulse API

Actions26

Overview

This node enables updating a project document within a project management system via the Pulse API. It is designed to modify existing documents associated with projects, allowing users to change key attributes such as the document's name, category, access rights, and linked project.

Common scenarios where this node is beneficial include:

  • Updating the title or classification of a project document after revisions.
  • Changing access permissions to control who can view or edit the document.
  • Associating the document with a different project if it was initially linked incorrectly.

For example, a project manager might use this node to update the "Training Book" document's name and restrict its access only to financial and lead users.

Properties

Name Meaning
Document ID * The unique identifier of the project document to update. This is required to specify which document will be modified.
Name * The new name for the document. This is a required field and represents the updated title or label of the document.
Category * The category of the document. Must be one of:
• Project Plan
• Training Book
• Client's Instruction
• Commercial Document
Rights * Access permissions for the document. Can be provided as either:
• A comma-separated list (e.g., "financial,lead,client,staff")
• An array of strings (e.g., ["financial", "lead"])

Access rules:
• Client users can add documents only with "client" right.
• Supervisors require the "lead" right.
• Financial users require the "financial" right.
Project ID * The identifier of the project to which the document belongs. This links the document to a specific project and is required.

Output

The node outputs a JSON object representing the updated project document. This typically includes fields such as the document's ID, name, category, rights, project association, and possibly metadata like timestamps or status.

No binary data output is indicated for this operation.

Dependencies

  • Requires an active connection to the Pulse API service.
  • Needs an API authentication token or API key credential configured in n8n to authorize requests.
  • The node depends on the Pulse API helper utilities bundled with the node implementation to perform the update operation.

Troubleshooting

  • Error: "The operation 'updateProjectDocument' is not supported for resource 'projectDocuments'!"
    This indicates a mismatch between the selected resource and operation. Ensure that the resource is set to "Project Document" and the operation to "Update Project Document".

  • Missing required properties error
    Make sure all required fields (Document ID, Name, Category, Rights, Project ID) are provided and correctly formatted.

  • Access permission errors
    If the rights string does not comply with the access rules (e.g., missing "lead" for supervisors), the API may reject the update. Verify the rights input matches the expected roles.

  • API authentication failures
    Confirm that the API key or token is valid and has sufficient permissions to update project documents.

Links and References

Discussion