Actions38
- Chatbot Actions
- Contact Actions
- Message Actions
- Panel Actions
- Sequence Actions
- Session Actions
Overview
The node interacts with the WTS Chat API to manage sequences and their contacts. Specifically, for the "Sequence" resource and the "Get Contacts By Sequence" operation, it retrieves all contacts associated with a given sequence ID. This is useful in scenarios where you want to automate workflows based on contact lists tied to specific marketing or communication sequences.
Practical examples include:
- Fetching all contacts enrolled in a particular email or messaging campaign sequence.
- Using the retrieved contacts to trigger follow-up actions or personalized messages.
- Integrating sequence contact data into CRM or marketing automation systems.
Properties
| Name | Meaning |
|---|---|
| Sequence ID | The unique identifier of the sequence for which to retrieve associated contacts. |
Output
The output is an array of JSON objects under the json field, each representing a contact associated with the specified sequence. The exact structure depends on the WTS Chat API response but typically includes contact details such as contact ID, phone number, name, and other metadata related to the contact within the sequence.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the WTS Chat API via an API key credential.
- The node expects the API key to be configured in n8n credentials for authentication.
- Network access to
https://api.wts.chatis necessary.
Troubleshooting
- Empty or missing Sequence ID: If the "Sequence ID" property is empty or only whitespace, the node throws an error indicating that the SequenceID is empty and must be filled in.
- API errors: Any issues communicating with the WTS Chat API (e.g., invalid API key, network issues, or invalid sequence ID) will result in an error wrapped as a NodeApiError. Check the API key validity and network connectivity.
- Unexpected response format: If the API returns unexpected data, downstream nodes may fail. Ensure the sequence ID is correct and the API service is operational.
Links and References
- WTS Chat API Documentation (general reference; actual endpoint docs not included in source)
- n8n documentation on Creating Custom Nodes