Pulse Workflow icon

Pulse Workflow

Workflow actions from Pulse API

Overview

This node interacts with a project management API to perform various actions related to project data, including showing or hiding specific pieces of project data. The "Show/Hide Project Data" operation allows users to update the visibility status of a particular data item within a project, effectively controlling whether that data is visible or hidden in the project context.

Common scenarios for this node include:

  • Managing metadata or custom fields associated with projects where certain data should be conditionally visible.
  • Automating updates to project data visibility based on workflow triggers or external events.
  • Integrating project data visibility controls into larger automation workflows for project management.

For example, you might use this node to hide sensitive project information from general team members while keeping it accessible to project managers, or to toggle visibility of data fields as part of a project phase transition.

Properties

Name Meaning
Data ID * The unique identifier of the project data item to update.
Key * The key name of the data field being updated.
Value * The value to assign to the data field.
Label * A human-readable label describing the data field.
Visibility Boolean flag indicating whether the project data should be shown (true) or hidden (false).

Note: The properties marked with * are required.

Output

The node outputs JSON data representing the result of the visibility update operation on the project data. This typically includes confirmation of the updated data item's state and any relevant metadata returned by the API.

No binary data output is involved in this operation.

Dependencies

  • Requires an API key credential for authenticating with the Pulse API service.
  • The node depends on the Pulse API helper utilities bundled with the node implementation to communicate with the backend service.
  • Proper configuration of the API credentials in n8n is necessary for successful execution.

Troubleshooting

  • Common Issues:

    • Invalid or missing Data ID can cause the operation to fail because the target data item cannot be identified.
    • Incorrect API credentials or expired tokens will result in authentication errors.
    • Attempting to update visibility on non-existent or inaccessible project data may lead to errors.
  • Error Messages:

    • "The operation "updateProjectDataVisibility" is not supported for resource "projectData"!" indicates a misconfiguration or unsupported operation selection.
    • API error messages related to authorization failures suggest checking the API key credential setup.
    • Validation errors about missing required parameters (e.g., Data ID, Key) require ensuring all mandatory inputs are provided.

To resolve these issues, verify input parameters, ensure valid API credentials, and confirm that the targeted project data exists and is accessible.

Links and References

Discussion