CoachTrigger Dev icon

CoachTrigger Dev

Interact with coach trigger action development server API

Actions16

Overview

This node interacts with the Coach Trigger development server API to retrieve and manage activity-related data for a company. Specifically, the "Company: Get Team Activities List" operation fetches a list of activities associated with a specified team within the company.

Common scenarios where this node is beneficial include:

  • Retrieving all activities assigned or relevant to a particular team for reporting or monitoring purposes.
  • Integrating team activity data into workflows for performance tracking or notifications.
  • Automating data collection about team engagements in coaching or CRM systems.

For example, a manager could use this node to automatically pull the latest activities for their team and generate a summary report or trigger follow-up actions based on activity status.

Properties

Name Meaning
Authentication Method of authentication to use when connecting to the API. Options: "Company Api", "System Api".
Team ID The unique identifier of the team for which to retrieve the activities list.

Output

The output is an array of JSON objects representing the response from the API call that retrieves the team activities list. Each item in the output corresponds to one activity or a related data structure as returned by the external API.

The exact structure depends on the API response but generally includes details about each activity such as IDs, names, statuses, dates, or other metadata relevant to team activities.

No binary data output is produced by this operation.

Dependencies

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

Troubleshooting

  • Authentication errors: Ensure that the correct API key credential is selected and properly configured. Using the wrong authentication method or expired keys will cause authorization failures.
  • Missing or invalid Team ID: The Team ID parameter is required. Providing an empty or incorrect Team ID will result in API errors or empty responses.
  • API request failures: Network issues or API downtime can cause request failures. Check connectivity and API status.
  • Unexpected response format: If the API changes its response schema, the node output may not match expectations. Verify API documentation and update workflows accordingly.

Links and References

Discussion