Actions16
- User Actions
- Activity Actions
- Message Actions
Overview
This node interacts with the CoachTrigger API to retrieve and manage activity-related data for teams, users, and companies. Specifically, the "Company: Get Team Activities List" operation fetches a list of activities associated with a particular team within a company.
Use cases include:
- Retrieving all activities assigned or relevant to a specific team to monitor progress or performance.
- Integrating team activity data into workflows for reporting or analytics.
- Automating notifications or follow-ups based on team activities.
For example, a manager could use this node to automatically pull the latest activities for their team and generate a summary report or trigger alerts for overdue tasks.
Properties
| Name | Meaning |
|---|---|
| Authentication | Choose between two authentication methods: "Company Api" (using an API key) or "System Api". |
| Team ID | The unique identifier of the team whose activities you want to retrieve. This is required. |
Output
The node outputs JSON data containing the list of activities for the specified team as returned by the CoachTrigger API. The structure depends on the API response but generally includes details about each activity such as IDs, names, statuses, dates, and other metadata related to team activities.
No binary data output is involved in this operation.
Dependencies
- Requires access to the CoachTrigger API.
- Needs valid credentials depending on the selected authentication method:
- For "Company Api": an API key credential with
companyIdandapiKey. - For "System Api": a different API key credential with a
keyproperty.
- For "Company Api": an API key credential with
- The node makes HTTP POST requests to endpoints under
https://www.coachtriggerapp.com/crmApi/.
Troubleshooting
- Authentication errors: Ensure that the correct authentication method is selected and that the corresponding API keys are valid and have necessary permissions.
- Missing or invalid Team ID: The Team ID is required; verify it is correctly provided and corresponds to an existing team.
- API request failures: Network issues or incorrect endpoint usage can cause errors. Check connectivity and confirm the API endpoint URL.
- Unexpected response format: If the API changes its response structure, parsing errors may occur. Review API documentation for updates.
Links and References
- CoachTrigger API Documentation (assumed location, please verify)
- n8n HTTP Request Node documentation for understanding how HTTP calls are made within n8n workflows.