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 a project management API to retrieve various indicators related to projects. Specifically, the "Show project indicators" operation fetches indicator data for a specified project over a defined time period. This is useful for monitoring project performance metrics such as progress, resource usage, or other custom indicators tracked by the system.
Common scenarios include:
- Generating reports on project health and status over daily, weekly, monthly, or quarterly periods.
- Filtering indicators by specific criteria like member accounts or custom selectors to analyze subsets of project data.
- Integrating project indicator data into dashboards or automated workflows for real-time monitoring.
For example, a project manager could use this node to pull monthly productivity indicators for a project to assess team performance and adjust resources accordingly.
Properties
| Name | Meaning |
|---|---|
| Project ID * | The unique identifier of the project to retrieve indicators for. |
| Period * | The time interval for which to get indicators. Options: Daily, Weekly, Monthly, Quarterly. |
| Indicator Name * | The specific indicator to retrieve (e.g., progress, budget usage). Loaded dynamically based on project. |
| From * | The start date/time of the period to fetch indicators from. |
| To * | The end date/time of the period to fetch indicators until. |
| Additional Filters | Optional filters to narrow down the indicator data: |
| - Selector | A filter selector loaded dynamically based on project and indicator name. |
| - Member Account ID | Filter indicators by a specific member account ID. |
(* indicates required fields)
Output
The node outputs JSON data containing the requested project indicators within the specified period and filters. The structure typically includes:
- Indicator values keyed by date or period segment.
- Metadata about the indicator such as name and description.
- Possibly aggregated or raw data points depending on the API response.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential for authenticating with the Pulse API service.
- The node depends on dynamic loading methods to populate options for indicators and selectors based on the selected project.
- Proper configuration of the API credentials in n8n is necessary for successful requests.
Troubleshooting
Common issues:
- Invalid or missing Project ID will cause errors fetching indicators.
- Date range ("From" and "To") must be valid ISO date strings; invalid dates may cause request failures.
- Selecting an indicator name before choosing a project may result in empty option lists due to dependency on project context.
- Network or authentication errors if API credentials are misconfigured or expired.
Error messages:
"The operation "getProjectIndicator" is not supported for resource "projectIndicators"!"— indicates a mismatch in operation/resource selection.- API errors returned in JSON under
errorfield whencontinueOnFailis enabled.
Resolutions:
- Verify all required fields are filled correctly.
- Ensure API credentials are valid and have sufficient permissions.
- Check date formats and logical ranges.
- Reload indicator options after selecting a project to ensure correct dependencies.
Links and References
- Pulse API Documentation (replace with actual URL)
- n8n documentation on Creating Custom Nodes
- General best practices for Date and Time Handling in APIs