CoachTrigger Dev icon

CoachTrigger Dev

Interact with coach trigger action development server API

Actions16

Overview

This node interacts with a Coach Trigger development server API to retrieve and manage user activity data, including daily report data. Specifically, the "Get Daily Report DATA" operation fetches detailed daily report information for a specified user on a given date. This is useful in scenarios where you want to automate the retrieval of daily performance or activity summaries for users within a coaching or team management platform.

Practical examples:

  • Automatically pulling daily activity reports for employees or team members to monitor progress.
  • Integrating daily report data into dashboards or notifications.
  • Using daily report data as input for further automation or analytics workflows.

Properties

Name Meaning
Authentication Choose between "Company Api" (using a company API key) or "System Api" (using a system API key) for authenticating requests.
User ID The unique identifier of the user for whom the daily report data will be retrieved.
Date The specific date for which the daily report data is requested (format typically YYYY-MM-DD).

Output

The node outputs JSON data containing the daily report details for the specified user and date. The exact structure depends on the API response but generally includes metrics, activities, or KPIs relevant to that day’s report.

No binary data output is involved in this operation.

Example output JSON snippet might look like:

{
  "user_id": "12345",
  "date": "2024-06-01",
  "activities": [...],
  "kpi_values": {...},
  "summary": "Daily report summary text"
}

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://dev.mymatrixapp.com/crmApi/report/daily-data.
  • Proper configuration of these credentials in n8n is necessary before use.

Troubleshooting

  • Authentication errors: Ensure the correct API key type is selected and the key is valid and active.
  • Missing required parameters: The "User ID" property is mandatory; missing it will cause request failures.
  • Invalid date format: The "Date" should be in a proper string format (e.g., ISO 8601). Incorrect formats may lead to empty or error responses.
  • API connectivity issues: Network problems or incorrect endpoint URLs can cause request failures.
  • Unexpected response format: If the API changes its response structure, parsing errors may occur.

To resolve these issues:

  • Double-check API keys and permissions.
  • Validate all input parameters before execution.
  • Test connectivity to the API endpoint outside n8n if needed.
  • Review API documentation for any updates.

Links and References

Discussion