WTS Chat icon

WTS Chat

Get data from Wts API

Actions39

Overview

The WTS Chat node for n8n allows you to interact with the Wts API, specifically managing contacts, messages, sessions, panels, sequences, and chatbots.
For the Contact resource and the Get By ID operation, this node retrieves detailed information about a specific contact using its unique Contact ID. This is useful in scenarios where you need to fetch up-to-date details of a contact for further automation steps, such as personalizing communication, updating records, or integrating with CRM systems.

Example use cases:

  • Fetching a contact's full profile before sending them a message.
  • Retrieving custom fields or tags associated with a contact for segmentation.
  • Validating contact existence and details during workflow execution.

Properties

Below are the input properties relevant to the "Contact" resource and "Get By ID" operation:

Display Name Type Description
Contact ID String The unique identifier of the contact to retrieve.
Include Details Multi Options Additional details to include in the response. Options: Tags, CustomFields.

Output

The output will be a single item per execution, with the following structure:

{
  "json": {
    // All available data for the specified contact,
    // including standard fields (e.g., name, email, phone) and,
    // if requested via "Include Details", arrays/objects for tags and custom fields.
    // The exact structure depends on the Wts API response.
  }
}
  • If "Include Details" is set, the output may contain additional fields such as:
    • tags: An array of tag objects associated with the contact.
    • customFields: An object or array representing custom field values.

No binary data is produced by this operation.

Dependencies

  • External Service: Requires access to the Wts API.
  • API Key: You must configure valid Wts API credentials (wtsApi) in your n8n instance.
  • Environment: Internet access from the n8n host to https://api.wts.chat.

Troubleshooting

Common Issues:

  • Invalid Contact ID: If the provided Contact ID does not exist or is empty, the node will throw an error.
  • Missing Credentials: If the Wts API credentials are not configured or invalid, the request will fail.
  • API Errors: Any errors returned by the Wts API (such as permission issues or server errors) will be surfaced as node errors.

Error Messages & Resolutions:

  • "ContactID is empty, please fill it in": Ensure you provide a valid Contact ID.
  • "Invalid API key" or authentication errors: Check your Wts API credentials in n8n.
  • Other errors: Review the error message for details; often, they relate to network issues or misconfiguration.

Links and References

Discussion