Actions39
- Chatbot Actions
- Contact Actions
- Message Actions
- Panel Actions
- Sequence Actions
- Session Actions
Overview
The "Get Contacts By Sequence" operation in the WTS Chat n8n node retrieves all contacts associated with a specific sequence. This is useful for automation scenarios where you need to process, analyze, or take action on users enrolled in a particular messaging or marketing sequence.
Common use cases:
- Fetching all leads or customers currently in a drip campaign.
- Segmenting users by their sequence participation for targeted follow-ups.
- Auditing or exporting contact lists from specific sequences.
Example:
You might use this node to pull all contacts from a "Welcome Series" sequence and then send them a survey or export their data to another system.
Properties
| Display Name | Type | Description |
|---|---|---|
| Sequence ID | String | The unique identifier of the sequence whose contacts you want to retrieve. Required for this operation. |
Output
The output will be an array of objects under the json field, each representing a contact associated with the specified sequence. The exact structure of each contact object depends on the API response, but typically includes fields such as:
{
"id": "contact_id",
"name": "Contact Name",
"email": "contact@example.com",
"phonenumber": "+1234567890",
// ...other contact details
}
- Each item in the output array corresponds to one contact.
- No binary data is produced by this operation.
Dependencies
- External Service: Requires access to the WTS Chat API.
- API Key: You must configure valid WTS API credentials (
wtsApi) in your n8n instance. - Environment: Ensure your n8n instance can reach
https://api.wts.chat.
Troubleshooting
Common Issues:
Missing or Invalid Sequence ID:
- Error:
"SequenceID is empty!"
Solution: Make sure you provide a valid Sequence ID in the input property.
- Error:
Authentication Errors:
- If your API key is missing or invalid, the node will fail to connect to the WTS API.
Solution: Check your credentials configuration in n8n.
- If your API key is missing or invalid, the node will fail to connect to the WTS API.
Network/Connectivity Issues:
- If n8n cannot reach the WTS API endpoint, ensure network/firewall settings allow outbound HTTPS requests.
Error Handling:
All errors are reported as n8n NodeApiError messages, which include a message and description for easier debugging.