WTS Chat

Overview

This node integrates with the WTS Chat API to perform various operations related to contacts, messages, sessions, and panels. Specifically for the Contact resource and the Get By Phone operation, it retrieves contact information by querying the API using a phone number.

Common scenarios where this node is beneficial include:

• Looking up customer or user details based on their phone number.
• Automating workflows that require fetching contact data dynamically during communication processes.
• Integrating contact retrieval into CRM or support systems to enrich data or trigger further actions.

For example, you could use this node in an automation that receives a phone number from a form submission or chat message, then fetches the corresponding contact details to personalize responses or update records.

Properties

Output

The output of the node is a JSON object containing the contact data retrieved from the API endpoint /core/v1/contact/phonenumber/{phoneNumber}.

• The json field contains the full contact information as returned by the API.
• The structure depends on the API response but typically includes fields such as contact ID, name, email, phone number, tags, annotations, custom fields, and metadata.
• No binary data output is produced by this operation.

Example output snippet (simplified):

{
  "id": "contact-id",
  "name": "John Doe",
  "email": "john.doe@example.com",
  "phonenumber": "+1234567890",
  "tags": [...],
  "customFields": {...},
  "metadata": {...}
}

Dependencies

• Requires an active connection to the WTS Chat API via an API key credential.
• The API base URL used is https://api-test.helena.run.
• The node uses HTTP GET requests with Bearer token authorization to fetch contact data.
• Proper configuration of the API key credential in n8n is necessary for authentication.

Troubleshooting

• Empty or no data returned:
  Ensure the phone number is correctly formatted and exists in the system. Also verify that the API key credential is valid and has sufficient permissions.

• Authentication errors:
  Check that the API key credential is correctly set up and not expired. Confirm that the API endpoint URL is reachable from your environment.

• Network or timeout issues:
  Verify network connectivity to the API server. If behind a proxy or firewall, ensure proper access rules are configured.

• Invalid phone number format:
  The API may reject improperly formatted phone numbers. Use international format if required.

• Unhandled exceptions:
  The node silently catches errors in the code; if no output appears, check the execution logs for error details.

Links and References

• WTS Chat API Documentation (Assumed based on base URL, please replace with actual docs if available)
• n8n Expressions Documentation
• n8n Credential Setup Guide

This summary focuses exclusively on the Contact resource's Get By Phone operation as requested.