Pulse Workflow icon

Pulse Workflow

Workflow actions from Pulse API

Overview

This node interacts with the Pulse API to perform various workflow actions related to project indicators, specifically including retrieving keys for project indicators. The "Get Project Indicator Keys" operation fetches the available indicator keys associated with a specified project. This is useful when you want to dynamically discover which indicators are available for a project, for example, to build dashboards, reports, or trigger automations based on specific project metrics.

Practical examples:

  • Automatically fetching all indicator keys of a project to populate dropdowns in subsequent workflow steps.
  • Integrating project performance data by first retrieving indicator keys and then querying their values.
  • Monitoring project health by periodically checking available indicators and their statuses.

Properties

Name Meaning
Project ID * The unique identifier of the project for which to retrieve the indicator keys. Required.

Output

The output contains a JSON object representing the list of project indicator keys retrieved from the Pulse API for the specified project. The exact structure depends on the API response but typically includes an array of indicator key objects or strings that identify each indicator.

No binary data output is produced by this operation.

Example output (conceptual):

{
  "indicatorKeys": [
    "budget",
    "progress",
    "riskLevel",
    ...
  ]
}

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 handle authentication and API requests.
  • Network access to the Pulse API endpoint is necessary.

Troubleshooting

  • Common issues:

    • Invalid or missing Project ID: Ensure the Project ID is correctly provided and corresponds to an existing project.
    • Authentication errors: Verify that the API key credential is valid and has sufficient permissions.
    • Network connectivity problems: Confirm that the n8n instance can reach the Pulse API servers.
  • Error messages:

    • "The operation "getProjectIndicatorKeys" is not supported for resource "projectIndicators"!"
      This indicates a mismatch between selected resource and operation; ensure both are set correctly.
    • Errors containing "error" in the output JSON usually indicate API request failures; check the error message for details.
    • If the node throws an error about unsupported resources or operations, verify that the node version supports the requested action.

Links and References

Discussion