Actions23
- Activities Actions
- Project Actions
- Project Member Actions
- Project Document Actions
- Project Data Actions
- Project Work Unit Actions
Overview
This node integrates with the Pulse API to manage project-related data within workflows. Specifically, for the Project Data resource and the Add Project Data operation, it allows users to add custom key-value pairs labeled with descriptive text to a specified project. This is useful for storing additional metadata or configuration details related to projects that are not covered by default fields.
Practical scenarios include:
- Adding custom attributes to projects such as client-specific codes, internal notes, or status flags.
- Storing configuration parameters or settings relevant to a project.
- Enhancing project records with searchable labels and values for reporting or automation purposes.
Properties
Name | Meaning |
---|---|
Project ID * | The unique identifier of the project to which the data will be added. |
Key * | The key name for the data entry, representing the attribute or field name. |
Value * | The value associated with the key, representing the data content. |
Label * | A human-readable label describing the data entry, useful for identification or display. |
(* indicates required fields)
Output
The node outputs JSON data representing the result of adding the project data entry. This typically includes confirmation of the created data record with its key, value, label, and possibly metadata such as timestamps or identifiers assigned by the Pulse system.
No binary data output is involved in 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 on the Pulse account to create or modify project data entries are necessary.
Troubleshooting
Common Issues:
- Invalid or missing Project ID: Ensure the project ID provided exists and is correctly formatted.
- Insufficient permissions: The API key used must have rights to modify project data.
- Duplicate keys: If the same key already exists for the project, the API might reject the creation or overwrite depending on API behavior.
Error Messages:
"The operation "createProjectData" is not supported for resource "projectData"!"
— Indicates a mismatch between selected resource and operation; verify correct selections.- API authentication errors: Check that the API key credential is valid and has not expired.
- Network or connectivity issues: Verify network access to the Pulse API endpoint.
Resolving these usually involves verifying input parameters, checking API credentials, and ensuring the Pulse account has appropriate access.
Links and References
- Pulse API Documentation (Replace with actual URL if available)
- n8n Documentation on Creating Custom Nodes
- General API Authentication Best Practices