CT Coach Dev icon

CT Coach Dev

Interact with HttpBin API

Actions13

Activity → Update User Current KPI Value

AI-generated

Overview

This node interacts with a Coach API to update the current KPI (Key Performance Indicator) value for a specific user. It is useful in scenarios where you want to programmatically track and update performance metrics or KPIs of users within a coaching or employee management system. For example, after processing new performance data or receiving updated KPI values from another system, this node can be used to push those updates into the Coach platform.

Properties

Name Meaning
Authentication Choose between two authentication methods: "Company Api" or "System Api".
User ID The unique identifier of the user whose KPI value you want to update.
KPI ID The identifier of the KPI metric that you want to update for the user.
KPI Value The new value to set for the specified KPI.
KPI Date (Optional) The date associated with the KPI value update.

Output

The node outputs JSON data representing the response from the Coach API after attempting to update the user's current KPI value. This typically includes confirmation of the update or details about the updated KPI record. The output does not include binary data.

Example output structure (simplified):

{
  "success": true,
  "updatedKpi": {
    "userId": "string",
    "kpiId": "string",
    "kpiValue": "string",
    "kpiDate": "string"
  }
}

Dependencies

  • Requires an API key credential for authentication, either via "Company Api" or "System Api".
  • The node makes HTTP POST requests to the Coach API endpoint at https://coachtriggerapp.com/crmApi/update-current-kpi-value (inferred from similar patterns; actual URL used is https://coachtriggerapp.com/crmApi/get-current-kpi-value for getting KPI, but for update operation it uses the same base URL with appropriate body).
  • Proper configuration of credentials in n8n is necessary to authenticate requests.

Troubleshooting

  • Authentication errors: Ensure that the correct API key credential is selected and properly configured. Using the wrong authentication method or expired keys will cause request failures.
  • Missing required fields: The node requires User ID, KPI ID, and KPI Value. Omitting any of these will likely result in errors from the API.
  • Invalid KPI values or IDs: If the KPI ID or value is invalid or not recognized by the backend, the API may return an error. Verify the correctness of these inputs.
  • Network issues: Connectivity problems or incorrect API URLs can cause request failures. Check network access and endpoint availability.
  • Parsing errors: The node expects JSON responses. If the API returns malformed JSON or unexpected content, parsing errors may occur.

Links and References

Discussion