Actions38
- Chatbot Actions
- Contact Actions
- Message Actions
- Panel Actions
- Sequence Actions
- Session Actions
Overview
The node interacts with the "Sequence" resource of the WTS Chat API, specifically supporting operations to manage contacts within sequences. The "Remove Contact To Sequence" operation allows users to remove a single contact from a specified sequence by providing either the contact's ID or phone number along with the sequence ID.
This node is beneficial in scenarios where automated workflows need to dynamically manage contact lists within marketing or communication sequences, such as unsubscribing a user from a campaign or cleaning up contact lists based on certain triggers.
Example use case:
- Automatically removing a customer from a follow-up message sequence after they have made a purchase or opted out.
Properties
| Name | Meaning |
|---|---|
| Sequence ID | The unique identifier of the sequence from which the contact will be removed. |
| Contact ID | The unique identifier of the contact to remove from the sequence. |
| Phone Number | The phone number of the contact to remove from the sequence (alternative to Contact ID). |
Note: Either Contact ID or Phone Number must be provided to identify the contact to remove.
Output
The output is a JSON object representing the response from the WTS Chat API after attempting to remove the contact from the sequence. This typically includes confirmation details about the removal operation, such as success status or any relevant metadata returned by the API.
The node does not output binary data for this operation.
Dependencies
- Requires an active connection to the WTS Chat API.
- Requires an API key credential configured in n8n for authentication.
- The base URL for API requests is
https://api.wts.chat.
Troubleshooting
Error: "SequenceID is empty!"
Occurs if the Sequence ID property is not filled. Ensure that the Sequence ID is provided and valid.Error: "Remove a contact either by ID or phone number"
Happens when neither Contact ID nor Phone Number is provided. Provide at least one to identify the contact.API errors related to invalid IDs or permissions
Verify that the API key has sufficient permissions and that the provided IDs exist and are correct.Network or connectivity issues
Check internet connection and API endpoint accessibility.
Links and References
- WTS Chat API Documentation (generic placeholder, replace with actual URL if available)
- n8n Documentation on Creating Custom Nodes