CoachTrigger Live icon

CoachTrigger Live

Interact with coach trigger action liveelopment server API

Actions16

Overview

This node interacts with the CoachTrigger API to retrieve the daily report status for a specific user on a given date. It is useful in scenarios where you want to monitor or track the progress and status of a user's daily activities or coaching reports within a coaching or performance management system.

For example, a manager could use this node to automatically fetch the daily report status of an employee to check if they have completed their assigned coaching activities or to trigger follow-up actions based on the report status.

Properties

Name Meaning
Authentication Method of authentication to use: "Company Api" (using company API key) or "System Api".
User ID The unique identifier of the user for whom the daily report status is requested.
Date The specific date for which the daily report status should be retrieved (optional).

Output

The output is a JSON object containing the response from the CoachTrigger API endpoint /crmApi/report/daily-status. This typically includes the status details of the daily report for the specified user and date.

The exact structure depends on the API response but generally will include fields indicating the completion status, timestamps, and possibly summary data related to the user's daily activities.

No binary data output is produced by this operation.

Dependencies

  • Requires access to the CoachTrigger API.
  • Requires either a "Company Api" or "System Api" authentication credential configured in n8n.
  • Network connectivity to https://www.coachtriggerapp.com is necessary.

Troubleshooting

  • Authentication errors: Ensure that the correct API key or system key is provided and valid.
  • Missing required parameters: The User ID is mandatory; ensure it is set correctly.
  • Invalid date format: The Date parameter should be in a format accepted by the API (usually ISO 8601).
  • API request failures: Check network connectivity and API availability.
  • Unexpected response format: If the API changes, the node might fail to parse the response; verify API documentation for updates.

Links and References

Discussion