Actions26
- Activities Actions
- Project Actions
- Project Member Actions
- Project Document Actions
- Project Data Actions
- Project Work Unit Actions
- Project Indicators Actions
Overview
This node interacts with project data within a Pulse API environment, specifically allowing users to show or hide project data entries. It is useful in scenarios where managing the visibility of specific pieces of project-related information is necessary, such as controlling which data points are publicly accessible or hidden from certain views.
For example, a project manager might want to hide sensitive project data from general team members while keeping it visible to stakeholders. This node enables toggling the visibility status of such data programmatically within an automated workflow.
Properties
| Name | Meaning |
|---|---|
| Data ID * | The unique identifier of the project data entry to update. |
| Key * | The key associated with the project data entry. |
| Value * | The value assigned to the project data entry. |
| Label * | A descriptive label for the project data entry. |
| Visibility | Boolean flag to show (true) or hide (false) the project data entry in the project. |
Properties marked with * are required.
Output
The node outputs JSON data representing the result of the visibility update operation on the specified project data entry. This typically includes confirmation of the updated state or details of the modified project data.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the Pulse API via an API key credential.
- The node depends on the Pulse API helper utilities to perform authenticated requests.
- Proper configuration of the API authentication token in n8n credentials is necessary.
Troubleshooting
Common Issues:
- Providing an invalid or non-existent Data ID will cause the operation to fail.
- Missing required properties (Data ID, Key, Value, Label) will prevent execution.
- Insufficient permissions or incorrect API credentials can lead to authorization errors.
Error Messages:
"The operation "updateProjectDataVisibility" is not supported for resource "projectData"!"indicates a mismatch between selected operation and resource.- Errors related to API connectivity or authentication usually suggest checking the API key credential setup.
- Validation errors about missing parameters require ensuring all required fields are filled.
Resolving these issues generally involves verifying input parameters, ensuring correct resource-operation selection, and confirming valid API credentials.
Links and References
- Pulse API Documentation (replace with actual URL)
- n8n documentation on Creating Custom Nodes
- General API authentication best practices in n8n workflows