Actions26
- Activities Actions
- Project Actions
- Project Member Actions
- Project Document Actions
- Project Data Actions
- Project Work Unit Actions
- Project Indicators Actions
Overview
The node enables managing project-related data within a Pulse API environment, specifically allowing users to add new data entries to projects. This is useful for scenarios where you want to store custom key-value pairs associated with a project, such as metadata, configuration settings, or additional descriptive information.
For example, you might use this node to:
- Add a custom label and value pair to a project for tracking purposes.
- Store project-specific parameters that can be referenced later in workflows.
- Enhance project records with additional contextual data not covered by default fields.
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 identifier of the data item. |
| Value | The value corresponding to the key, representing the content or information stored. |
| Label | A human-readable label describing the data entry for easier identification. |
Output
The node outputs a JSON object representing the newly created project data entry. This typically includes the key, value, label, and any other metadata returned by the Pulse API confirming the creation of the data item.
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 within the node's codebase to perform authenticated requests.
- Proper permissions on the Pulse API side are necessary to create project data entries.
Troubleshooting
Common issues:
- Invalid or missing Project ID: Ensure the project ID provided exists and is correctly formatted.
- Missing required fields (Key, Value, Label): All these fields are mandatory; leaving them empty will cause errors.
- API authentication failures: Verify that the API key credential is valid and has sufficient permissions.
Error messages:
"The operation "createProjectData" is not supported for resource "projectData"!"— This indicates a misconfiguration in the operation selection; ensure the correct operation is chosen.- Network or authentication errors from the Pulse API will be surfaced; check credentials and network connectivity.
Resolution tips:
- Double-check all required input properties before execution.
- Confirm API credentials and permissions.
- Use the node’s “Continue On Fail” option to handle errors gracefully during batch processing.
Links and References
- Pulse API Documentation (replace with actual URL if available)
- n8n documentation on Creating Custom Nodes