CT Coach Dev icon

CT Coach Dev

Interact with HttpBin API

Actions13

User → Get User Data by CRM ID

AI-generated

Overview

This node interacts with the Coach API to retrieve user data based on a CRM User ID. Specifically, for the "User" resource and the "Get User Data by CRM ID" operation, it sends a POST request to the Coach API endpoint to fetch detailed information about a user identified by their CRM system ID.

This node is useful in scenarios where you need to synchronize or enrich your workflows with user data stored in an external CRM system managed by the Coach API. For example, you might want to pull user profile details into your automation to personalize communications, generate reports, or trigger other actions based on user attributes.

Properties

Name Meaning
Authentication Choose between two authentication methods: "Company Api" (using a company API key) or "System Api" (using a system API key).
CRM User ID The unique identifier of the user in the CRM system whose data you want to retrieve. This is a required string input.

Output

The node outputs JSON data representing the user information retrieved from the Coach API. The structure of this JSON depends on the API response but typically includes user profile details associated with the provided CRM User ID.

No binary data output is produced by this operation.

Example output JSON snippet (structure depends on API):

{
  "userId": "12345",
  "name": "John Doe",
  "email": "john.doe@example.com",
  "role": "Coach",
  "status": "Active"
}

Dependencies

  • Requires access to the Coach API at https://coachtriggerapp.com/crmApi/get-user-data.
  • Requires an API key credential configured in n8n, either as a "Company Api" or "System Api" key.
  • Proper credentials must be set up in n8n to authenticate requests.

Troubleshooting

  • Authentication errors: Ensure that the correct API key is selected and properly configured in n8n credentials. Using the wrong authentication option or expired keys will cause authorization failures.
  • Invalid CRM User ID: If the CRM User ID does not exist or is malformed, the API may return an error or empty data. Verify the correctness of the CRM User ID input.
  • Network issues: Connectivity problems or incorrect API endpoint URLs can cause request failures. Confirm network access and endpoint availability.
  • Unexpected API responses: If the API changes its response format, the node's output parsing might fail. Check for updates or changes in the Coach API documentation.

Links and References

  • Coach API Documentation (assumed URL for reference)
  • n8n HTTP Request Node documentation for understanding how HTTP calls are made within n8n workflows.

Discussion