CoachTrigger Live icon

CoachTrigger Live

Interact with coach trigger action liveelopment server API

Actions16

Overview

This node interacts with the CoachTrigger API to retrieve user data based on a CRM User ID within a company context. Specifically, the "Company: Get User Data by CRM ID" operation fetches detailed information about a user identified by their CRM system ID. This is useful in scenarios where you want to synchronize or enrich your workflows with user data stored in an external CRM system managed by CoachTrigger.

Practical examples include:

  • Automatically fetching user profile details when processing CRM leads.
  • Enriching customer support tickets with up-to-date user information from the CRM.
  • Integrating CRM user data into marketing automation workflows.

Properties

Name Meaning
Authentication Choose between two authentication methods: "Company Api" or "System Api".
CRM User ID The unique identifier of the CRM user whose data you want to retrieve (required).

Output

The node outputs a JSON object containing the user data returned by the CoachTrigger API for the specified CRM User ID. The structure of this JSON depends on the API response but generally includes user profile details such as name, contact information, and other CRM-related attributes.

No binary data output is produced by this operation.

Example output snippet (structure may vary):

{
  "userId": "12345",
  "name": "John Doe",
  "email": "[email protected]",
  "phone": "+1234567890",
  "company": "Example Corp",
  ...
}

Dependencies

  • Requires an API key credential for authentication, selectable as either "Company Api" or "System Api".
  • The node makes HTTP POST requests to https://www.coachtriggerapp.com/crmApi/get-user-data.
  • Proper configuration of the API credentials with valid companyId and apiKey or equivalent keys is necessary.

Troubleshooting

  • Authentication errors: Ensure that the correct API key credential is selected and properly configured. Invalid or missing keys will cause authorization failures.
  • Invalid CRM User ID: If the provided CRM User ID does not exist or is incorrect, the API may return an error or empty data. Verify the ID before running the node.
  • Network issues: Connectivity problems to the CoachTrigger API endpoint can cause request failures. Check network access and proxy settings if applicable.
  • Unexpected API responses: If the API returns unexpected data or errors, verify that the API version and endpoint URL have not changed.

Links and References

Discussion