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 update user-related data within a coaching or CRM system. Specifically for the User resource and the Get User Data operation, it fetches detailed user profile information from the Coach API based on a given user ID and optionally a coach ID.

Common scenarios where this node is beneficial include:

  • Retrieving user profile details for display or further processing in workflows.
  • Integrating user data from the Coach API into other systems or dashboards.
  • Automating user data retrieval as part of coaching or CRM automation pipelines.

Practical example:

  • A workflow that triggers when a new user is added in a CRM system and uses this node to fetch detailed coaching profile data for that user to personalize communications or reports.

Properties

Name Meaning
Authentication Choose between two authentication methods: "Company Api" (using an API key credential) or "System Api" (using a system key credential).
User ID The unique identifier of the user whose data you want to retrieve.
Coach ID (Optional) The unique identifier of the coach associated with the user, used to get more specific user profile data.

Output

The node outputs a JSON object containing the user profile data retrieved from the Coach API. The structure depends on the API response but typically includes user details such as name, contact info, coaching status, and related metadata.

No binary data output is produced by this operation.

Example output snippet (conceptual):

{
  "user_id": "12345",
  "name": "John Doe",
  "email": "[email protected]",
  "coach_id": "67890",
  "profile_details": {
    "status": "active",
    "last_session_date": "2024-05-01"
  }
}

Dependencies

  • Requires access to the Coach Trigger development server API at https://dev.mymatrixapp.com/crmApi/user/detail.
  • Requires either a company API key credential or a system API key credential configured in n8n for authentication.
  • Network connectivity to the API endpoint must be available.

Troubleshooting

  • Authentication errors: If the node returns unauthorized or forbidden errors, verify that the correct authentication method is selected and that the corresponding API keys are valid and have sufficient permissions.
  • Missing required parameters: Ensure that the "User ID" property is provided; otherwise, the API call will fail.
  • API response parsing errors: If the node fails to parse the response, check if the API endpoint is returning valid JSON and that there are no network issues.
  • Empty or unexpected data: Confirm that the user ID exists in the Coach API system and that the optional coach ID (if used) is correct.

Links and References

  • Coach API Documentation (hypothetical link based on domain)
  • n8n documentation on HTTP Request Node for understanding how API calls are made.
  • General best practices for managing API credentials securely in n8n workflows.

Discussion