WTS Chat

Overview

The node "WTS Chat" integrates with the Wts API to manage various resources related to chat, contacts, messages, panels, sessions, sequences, and chatbots. Specifically for the Contact resource with the Get By ID operation, it retrieves detailed information about a contact by its unique identifier. This is useful in scenarios where you need to fetch a specific contact's data from your CRM or messaging platform to use in workflows such as customer support automation, personalized marketing campaigns, or contact management.

For example, you might use this node to:

• Retrieve a contact’s profile and tags before sending a targeted message.
• Fetch custom fields associated with a contact to enrich your database.
• Use contact details to trigger conditional logic in an automation workflow.

Properties

Output

The output of the node is a JSON object representing the contact data retrieved from the Wts API. This includes standard contact fields such as name, email, phone number, Instagram handle, annotations, and potentially extended details like tags and custom fields if requested.

The structure typically looks like:

{
  "id": "string",
  "name": "string",
  "email": "string",
  "phonenumber": "string",
  "instagram": "string",
  "annotation": "string",
  "tagIds": ["string"],
  "customFields": {
    "key1": "value1",
    "key2": "value2"
  },
  "metadata": {
    "key": "value"
  }
}

No binary data output is produced by this operation.

Dependencies

• Requires an API key credential for authenticating with the Wts API.
• The node depends on the WtsCoreService.getContactById method to fetch contact data.
• Network access to https://api.wts.chat is required.

Troubleshooting

• Invalid or empty Contact ID: If the Contact ID parameter is empty or invalid, the node will throw an error indicating that the Contact ID must be provided.
• API authentication errors: If the API key is missing or invalid, the node will fail with an authentication error.
• Network issues: Connectivity problems to the Wts API endpoint can cause timeouts or failures.
• Unexpected API response: If the contact does not exist or the API returns an error, the node will throw an error with the API's message.

To resolve these issues:

• Ensure the Contact ID is correctly set and not empty.
• Verify that the API key credential is configured properly in n8n.
• Check network connectivity and firewall settings.
• Confirm the contact exists in the Wts system.

Links and References

• Wts API Documentation (general reference, actual docs URL may vary)
• n8n documentation on Credentials
• n8n documentation on Creating Custom Nodes