Actions16
- User Actions
- Activity Actions
- Message Actions
Overview
This node interacts with the CoachTrigger API to retrieve and manage user-related data within a coaching or CRM context. Specifically, for the "User" resource and the "Get User Data" operation, it fetches detailed profile information about a specified user from the Coach API.
Common scenarios where this node is beneficial include:
- Integrating user profile data into automated workflows.
- Synchronizing user information between CoachTrigger and other systems.
- Fetching user details dynamically during coaching or CRM processes.
For example, you might use this node to get a user's profile by their user ID and then use that data to personalize communications or update records in another system.
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 identifier of the coach associated with the user, used only when getting user profile data. |
Output
The node outputs JSON data containing the user profile information retrieved from the Coach API. The exact 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 involved in this operation.
Dependencies
- Requires access to the CoachTrigger API.
- Needs either a company API key or a system API key configured in n8n credentials.
- Network connectivity to
https://www.coachtriggerapp.com/crmApi/user/detailendpoint.
Troubleshooting
- Authentication errors: Ensure the correct API key or system key is provided and valid.
- Missing required parameters: The "User ID" must be supplied; otherwise, the request will fail.
- API response errors: If the API returns an error, verify the user ID exists and the account has permission to access the data.
- JSON parsing issues: The node expects JSON responses; if the API returns invalid JSON, check network issues or API status.
Links and References
- CoachTrigger API Documentation (hypothetical link for reference)
- n8n documentation on HTTP Request Node for understanding API calls in workflows