Actions8
- Collaborators Actions
- OKRs Actions
- KPIs Actions
- Plans Actions
Overview
The Acelera node is designed to interact with the Acelera API, specifically for managing Objectives and Key Results (OKRs). In the context of the "Add advance" operation for the OKRs resource, this node allows users to update the progress of a specific Key Result (KR) by providing an ID, a date, and a result value. This functionality is particularly beneficial for organizations that track their performance against set objectives, enabling them to keep their OKRs up-to-date in real-time. For example, a user might use this node to log the completion of a milestone on a Key Result, ensuring that all stakeholders have visibility into progress.
Properties
| Name | Meaning |
|---|---|
| KR ID | The unique identifier of the Key Result being updated. |
| Date | The date associated with the advancement of the Key Result, defaulting to "2025-09-27". |
| Result | The actual result or progress made towards the Key Result, which must be entered by the user. |
Output
The output of the Acelera node will be structured as JSON, containing the response from the Acelera API after attempting to update the Key Result. This typically includes details about the updated Key Result, such as its current status or any relevant metadata returned by the API. If the node can output binary data, it would generally represent files or images related to the Key Result, but this specific operation focuses on JSON output.
Dependencies
To utilize the Acelera node, users need to configure an OAuth2 API key credential for authentication with the Acelera API. Additionally, the node requires access to the internet to make HTTP requests to the Acelera API endpoints.
Troubleshooting
Common issues users might encounter include:
- Invalid KR ID: If the provided Key Result ID does not exist, the node may throw an error indicating that the Key Result could not be found. Users should verify the ID against existing Key Results.
- Authentication Errors: If the API key credential is incorrect or expired, users may receive authentication-related errors. Ensure that the correct API key is configured and that it has not expired.
- Network Issues: If there are connectivity problems, the node may fail to reach the Acelera API, resulting in timeout errors. Users should check their network connection and ensure that the Acelera API is accessible.
Links and References
- Acelera API Documentation (replace with actual documentation link)
- n8n Documentation for general guidance on using nodes and workflows.