CT Coach Dev icon

CT Coach Dev

Interact with HttpBin API

Overview

This node interacts with the Coach API to retrieve or update activity-related data for users, teams, and messages. Specifically, the "Get User Activities List" operation fetches a list of activities associated with a particular user. This is useful in scenarios where you want to analyze or display the activities a user has performed within a coaching or CRM system.

Practical examples include:

  • Displaying a user's recent activities on a dashboard.
  • Aggregating user activity data for performance reviews.
  • Integrating user activity logs into other workflows or reports.

Properties

Name Meaning
User ID ID of the user to get data for

The "User ID" property is required and specifies which user's activities will be retrieved.

Output

The node outputs an array of JSON objects representing the user activities returned by the Coach API. Each item in the output corresponds to one activity record associated with the specified user.

The exact structure of each activity object depends on the API response but typically includes details such as activity type, timestamps, and related metadata.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential and company ID credential to authenticate requests to the Coach API.
  • The node sends HTTP POST requests to the endpoint: https://dev.mymatrixapp.com/crmApi/get/user/activities.
  • Proper configuration of these credentials in n8n is necessary for successful execution.

Troubleshooting

  • Common issues:

    • Missing or invalid API credentials can cause authentication failures.
    • Providing an incorrect or non-existent User ID may result in empty responses or errors.
    • Network connectivity problems can prevent the node from reaching the API endpoint.
  • Error messages:

    • Authentication errors typically indicate invalid or missing API keys; verify credentials are correctly set.
    • HTTP 4xx or 5xx errors suggest issues with request parameters or server-side problems; check the User ID and API status.
    • Timeout errors may require increasing timeout settings or checking network stability.

Links and References

Discussion