CT Coach Dev icon

CT Coach Dev

Interact with HttpBin API

Actions13

Activity → Get Daily Report DATA

AI-generated

Overview

This node interacts with a coaching platform's API to retrieve various user activity and report data. Specifically, the "Get Daily Report DATA" operation fetches daily report information for a specified user on a given date. This is useful for scenarios where you want to automate the retrieval of daily performance or activity summaries for users, such as generating daily dashboards, sending automated reports, or integrating daily metrics into other systems.

For example, a manager could use this node to automatically pull daily activity reports for team members to monitor progress without manual intervention.

Properties

Name Meaning
Authentication Choose between two authentication methods: "Company Api" (using company API key) or "System Api" (using system API key).
User ID The unique identifier of the user for whom the daily report data is requested.
Date The specific date for which the daily report data should be retrieved (format expected by the API, typically YYYY-MM-DD).

Output

The output is a JSON object containing the daily report data for the specified user and date. The exact structure depends on the API response but generally includes metrics, activities, or KPIs tracked for that day.

  • The json field contains the parsed response from the API.
  • No binary data output is indicated for this operation.

Example output snippet (structure may vary):

{
  "user_id": "12345",
  "date": "2024-04-25",
  "activities": [...],
  "kpi_values": {...},
  "summary": {...}
}

Dependencies

  • Requires an API key credential for authentication, either a company-level API key or a system-level API key.
  • The node makes HTTP POST requests to the endpoint: https://coachtriggerapp.com/crmApi/report/daily-data.
  • Proper configuration of credentials in n8n is necessary to authenticate these requests.

Troubleshooting

  • Authentication errors: Ensure the correct API key is selected and configured. Using the wrong authentication method or expired keys will cause authorization failures.
  • Invalid User ID or Date: The API may return errors if the user ID does not exist or the date format is incorrect. Verify inputs before execution.
  • API response parsing errors: If the API returns malformed JSON or unexpected data, the node might fail to parse the response. Check the API status and response format.
  • Network issues: Connectivity problems can cause request failures. Confirm network access to the API endpoint.

Links and References

Discussion