CoachTrigger DevInstall

Overview

This node interacts with a Coach Trigger development server API to retrieve or update various user-related data, focusing on activities, messages, and reports. Specifically, the "Get User Questions List" operation fetches a list of questions associated with a particular user, optionally filtered by date.

Common scenarios for this node include:

• Retrieving user-specific questions for coaching or feedback purposes.
• Integrating user question data into workflows for analysis or reporting.
• Automating retrieval of daily or weekly user activity data alongside questions.

Practical example:

• A coaching platform wants to automatically pull all questions asked by a user on a specific date to analyze engagement or prepare personalized coaching sessions.

Properties

Output

The output is a JSON object containing the response from the API endpoint that provides the user's questions list. The structure depends on the API but generally includes an array or collection of question objects related to the specified user and date.

No binary data output is involved in this operation.

Example output snippet (conceptual):

{
  "questions": [
    {
      "questionId": "123",
      "content": "What are my goals for this week?",
      "dateAsked": "2024-04-20"
    },
    {
      "questionId": "124",
      "content": "How can I improve my productivity?",
      "dateAsked": "2024-04-20"
    }
  ]
}

Dependencies

• Requires access to the Coach Trigger development server API at https://dev.mymatrixapp.com/crmApi/user/questions.
• Requires an API key credential depending on the selected authentication method ("Company Api" or "System Api").
• Proper configuration of credentials within n8n is necessary to authenticate requests.

Troubleshooting

• Authentication errors: Ensure the correct API key or system key is configured and selected in the "Authentication" property.
• Missing required parameters: The "User ID" is mandatory; omitting it will cause request failures.
• Invalid date format: If specifying a date, ensure it matches the expected format by the API (usually ISO 8601).
• API response errors: Network issues or incorrect permissions may result in HTTP errors; verify API access rights and network connectivity.
• Parsing errors: The node attempts to parse JSON responses; malformed responses from the API could cause errors.

Links and References

• Coach Trigger API Documentation (hypothetical link, replace with actual if available)
• n8n documentation on HTTP Request Node for understanding API calls and authentication setup.