Actions38
- Chatbot Actions
- Contact Actions
- Message Actions
- Panel Actions
- Sequence Actions
- Session Actions
Overview
This node integrates with the WTS Chat API to manage contacts, messages, sessions, panels, 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 for further processing, such as updating records, sending targeted messages, or integrating contact details into workflows.
Practical examples:
- Fetching a contact's full profile including tags and custom fields before sending a personalized message.
- Retrieving contact details to update CRM records or trigger conditional logic based on contact attributes.
Properties
| Name | Meaning |
|---|---|
| Contact ID | The unique identifier of the contact to retrieve. |
| Include Details | Optional additional details to include in the response. Options: Tags, CustomFields. |
Output
The node outputs an array with one item containing a json object representing the contact data retrieved from the WTS API. The structure includes the contact's core information and, if requested, additional details such as tags and custom fields.
If the "Include Details" property includes:
Tags: The output will contain tag information associated with the contact.CustomFields: The output will include any custom fields defined for the contact.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating requests to the WTS Chat API.
- The base URL for API requests is
https://api.wts.chat. - The node depends on internal service modules that handle API calls (
WtsCoreService.getContactById).
Troubleshooting
- Invalid Contact ID: If the provided Contact ID does not exist or is malformed, the node will throw an error indicating the contact could not be found.
- API Key Issues: Missing or invalid API key credentials will cause authentication errors.
- Network Errors: Connectivity issues with the WTS API endpoint may result in request failures.
- Include Details Misconfiguration: Specifying unsupported options in "Include Details" might lead to incomplete or unexpected responses.
To resolve errors:
- Verify the Contact ID is correct and exists in the system.
- Ensure the API key credential is properly configured and valid.
- Check network connectivity and API availability.
- Use only supported options (
Tags,CustomFields) in the "Include Details" field.
Links and References
- WTS Chat API Documentation (Assumed official API docs)
- n8n documentation on Creating Custom Nodes