CoachTrigger Dev icon

CoachTrigger Dev

Interact with coach trigger action development server API

Actions16

Overview

This node interacts with a Coach Trigger development server API to retrieve and manage user-related data within a CRM system. Specifically, the "Company: Get User Data by CRM ID" operation fetches detailed user information based on a CRM user identifier. This is useful in scenarios where you need to synchronize or enrich CRM user data within your workflows, such as pulling user profiles for reporting, personalization, or integration with other systems.

Practical examples include:

  • Automatically retrieving user details when a new CRM record is created.
  • 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" (using an API key) or "System Api".
CRM User ID The unique identifier of the CRM user whose data you want to retrieve.

Output

The node outputs JSON data containing the user information retrieved from the CRM API. The structure depends on the external API response but generally includes user profile details such as name, contact info, status, and other CRM-specific attributes.

No binary data output is involved in this operation.

Example output snippet (structure depends on API):

{
  "userId": "12345",
  "name": "John Doe",
  "email": "[email protected]",
  "status": "active",
  ...
}

Dependencies

  • Requires access to the Coach Trigger development server API at https://dev.mymatrixapp.com/crmApi/get-user-data.
  • Requires valid credentials depending on the selected authentication method:
    • For "Company Api": an API key and company ID.
    • For "System Api": a trigger key.
  • These credentials must be configured in n8n prior to using the node.

Troubleshooting

  • Authentication errors: Ensure that the correct authentication method is selected and that the corresponding API keys or tokens are valid and have not expired.
  • Missing or invalid CRM User ID: The CRM User ID property is required; ensure it is provided and correctly formatted.
  • API request failures: Network issues or incorrect endpoint URLs can cause failures. Verify connectivity and endpoint correctness.
  • Unexpected response format: If the API changes its response structure, parsing errors may occur. Check the API documentation or update the node accordingly.

Links and References

Discussion