Flowyteam icon

Flowyteam

Custom node for Flowyteam API

Actions101

Overview

This node operation updates an existing OKR (Objectives and Key Results) Key Result in the Flowyteam system. It allows users to modify various attributes of a key result such as its owner, title, initial/current/target values, and additional optional fields like confidence level, description, leader, remarks, unit, and weight.

Typical use cases include:

  • Adjusting progress or details of a key result as work evolves.
  • Correcting or refining key result metadata for better tracking.
  • Updating measurement units or weights to reflect changes in priorities.

For example, a user might update the current value of a key result to reflect recent progress or add remarks explaining delays or challenges.

Properties

Name Meaning
Key Result ID The unique identifier of the key result to update.
KRS Owner The owner ID responsible for this key result.
KRS Title The title or name of the key result.
KRS Initial Value The starting value of the key result when it was created.
KRS Current Value The current measured value of the key result.
KRS Target Value The goal or target value that the key result aims to achieve.
Additional Fields Optional extra fields to provide more context or detail about the key result:
- KRS Confidence Confidence level indicating how likely the key result is to be achieved.
- KRS Description A textual description providing more information about the key result.
- KRS Leader The leader ID overseeing the key result.
- KRS Remarks Any remarks or notes related to the key result.
- KRS Unit The unit of measurement used for the key result values (e.g., %, $, hours).
- KRS Weight The relative importance or weight assigned to the key result within the objective.

Output

The node outputs JSON data representing the updated key result object as returned by the Flowyteam API. This typically includes all the updated fields along with metadata such as timestamps or IDs confirming the successful update.

No binary data output is involved.

Dependencies

  • Requires an active connection to the Flowyteam API via an API authentication token configured in n8n credentials.
  • The node depends on the Flowyteam service being available and accessible from the n8n environment.

Troubleshooting

  • Common Issues:

    • Invalid or missing Key Result ID will cause the update to fail.
    • Providing invalid data types (e.g., non-string where string expected) may cause errors.
    • Network or authentication failures can prevent communication with the Flowyteam API.
  • Error Messages:

    • "The operation 'update' is not supported for Key Result resource" — indicates a misconfiguration or unsupported operation.
    • API errors related to authorization usually mean the API key credential is missing or incorrect.
    • Validation errors from the API often indicate required fields are missing or contain invalid values.
  • Resolutions:

    • Ensure the Key Result ID is correct and exists in the system.
    • Verify all required fields are provided and correctly formatted.
    • Check API credentials and network connectivity.
    • Review any error messages returned by the API for specific field issues.

Links and References

  • Flowyteam API documentation (for detailed field definitions and API behavior)
  • n8n documentation on creating and using custom nodes
  • General OKR methodology resources for understanding key results and objectives

Discussion