Pulse Workflow icon

Pulse Workflow

Workflow actions from Pulse API

Actions23

Overview

This node enables updating a project document within a project management system via the Pulse API. It allows users to modify key attributes of an existing document associated with a project, such as its name, category, access rights, and linked project ID.

Common scenarios where this node is beneficial include:

  • Renaming or re-categorizing documents as project requirements evolve.
  • Adjusting access permissions to control who can view or edit the document.
  • Correcting metadata or linking the document to a different project.

Practical example: A project manager wants to update the category of a project plan document from "Project Plan" to "Training Book" and restrict access only to financial and lead users. This node facilitates that update programmatically in an automated workflow.

Properties

Name Meaning
Document ID * The unique identifier of the project document to update.
Name * The new name for the document.
Category * The category of the document. Options are:
• Project Plan
• Training Book
• Client's Instruction
• Commercial Document
Rights * Access permissions for the document. Can be provided as either:
• Comma-separated list (e.g., "financial,lead,client,staff")
• Array of strings (e.g., ["financial", "lead"])
Access rules apply based on user roles.
Project ID * The ID of the project to which the document belongs.

Output

The node outputs a JSON object representing the updated project document. This typically includes the updated fields such as document ID, name, category, rights, and project ID, reflecting the changes made.

No binary data output is indicated 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 bundled with the node implementation.
  • Proper permissions must be granted to the API key to perform document updates.

Troubleshooting

  • Common issues:

    • Providing an invalid or non-existent Document ID will result in an error.
    • Incorrect formatting of the Rights property (e.g., invalid role names or wrong data type) may cause permission errors.
    • Insufficient API permissions or expired credentials will prevent successful updates.

  • Error messages:

    • "The operation "updateProjectDocument" is not supported for resource "projectDocuments"!" — indicates a misconfiguration of resource or operation parameters.
    • API errors related to authorization or validation will be returned in the node output if "Continue On Fail" is enabled.

  • Resolution tips:

    • Verify the Document ID exists and is correct.
    • Ensure the Rights field follows the expected format and contains valid roles.
    • Confirm the API key has necessary scopes/permissions.
    • Enable "Continue On Fail" to capture errors without stopping the workflow.

Links and References

Discussion