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 the Pulse API to retrieve options for a specific project indicator within a given project. It is designed to fetch selectable values or configuration options related to an indicator, which can be useful when building dynamic workflows that depend on project metrics or KPIs.
Common scenarios include:
- Dynamically populating dropdowns in subsequent workflow steps based on available indicator options.
- Automating reporting or data processing tasks that require knowledge of valid indicator values.
- Integrating project performance metrics into broader automation pipelines.
For example, if you have a project with various indicators like "Budget Status" or "Completion Percentage," this node can fetch the possible options or states for those indicators to guide decision-making or trigger conditional logic.
Properties
| Name | Meaning |
|---|---|
| Project ID * | The unique identifier of the project for which to retrieve indicator options. |
| Indicator Name * | The name of the indicator whose options you want to get. This is selected from a list dynamically loaded based on the Project ID. |
Output
The node outputs JSON data containing the options available for the specified project indicator. The structure typically includes an array or object representing the possible values or configurations for that indicator.
Example output structure (conceptual):
{
"options": [
{
"name": "Option 1",
"value": "option_1"
},
{
"name": "Option 2",
"value": "option_2"
}
]
}
No binary data output is expected from 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's availability and correct permissions to access project indicators.
- The
Indicator Nameproperty options are dynamically loaded based on the providedProject ID, so the project must exist and be accessible.
Troubleshooting
Common issues:
- Invalid or missing Project ID: Ensure the Project ID is correct and the user has access rights.
- Indicator Name not loading: This may happen if the Project ID is incorrect or the project has no indicators defined.
- API authentication errors: Verify that the API key credential is correctly set up and has necessary permissions.
Error messages:
"The operation "getProjectIndicatorOptions" is not supported for resource "projectIndicators"!": This indicates a mismatch between the selected resource and operation; ensure both are correctly set.- Network or API errors: Check network connectivity and Pulse API status.
- Permission denied or unauthorized: Confirm API credentials and user permissions.
Resolving these usually involves verifying input parameters, checking API credentials, and ensuring the Pulse API service is operational.
Links and References
- Pulse API Documentation (replace with actual URL)
- n8n documentation on Creating Custom Nodes
- General API authentication setup in n8n: Credentials