Actions39
- Chatbot Actions
- Contact Actions
- Message Actions
- Panel Actions
- Sequence Actions
- Session Actions
Overview
The "Remove Contacts To Sequence" operation in the Sequence resource allows users to remove multiple contacts from a specified sequence in bulk. This is useful for managing contact lists within automated messaging or marketing sequences, ensuring that contacts who should no longer receive sequence messages are efficiently removed.
Typical use cases include:
- Cleaning up sequences by removing contacts who have opted out.
- Managing contact lists dynamically based on user behavior or status changes.
- Automating sequence membership updates as part of larger workflows.
For example, if you have a promotional message sequence and some contacts unsubscribe, you can use this operation to remove those contacts by their phone numbers or contact IDs from the sequence.
Properties
| Name | Meaning |
|---|---|
| Sequence ID | The unique identifier of the sequence from which contacts will be removed. |
| Phonenumbers | A collection of one or more phone numbers representing contacts to remove from the sequence. |
| Contacts ID | A collection of one or more contact IDs representing contacts to remove from the sequence. |
Note: At least one of "Phonenumbers" or "Contacts ID" must be provided to specify which contacts to remove.
Output
The node outputs JSON data containing the response from the API after attempting to remove the specified contacts from the sequence. The structure typically includes confirmation of removal or details about the updated sequence state.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the WTS Chat API.
- The node depends on the external WTS Chat service API endpoints to perform sequence and contact management operations.
- Proper configuration of the API key credential in n8n is necessary.
Troubleshooting
- Missing Sequence ID: If the Sequence ID is empty or invalid, the node will throw an error indicating the field must be filled.
- No Contacts Specified: If neither phone numbers nor contact IDs are provided, the node throws an error instructing to add contacts either by ID or phone number.
- API Errors: Any issues returned by the external API (e.g., network errors, permission issues) will be surfaced as node errors. Check API key validity and permissions.
- Rate Limiting: The code includes a delay between executions when processing multiple items, but excessive requests may still hit rate limits; consider batching inputs accordingly.
Links and References
- WTS Chat API Documentation (general reference for API endpoints)
- n8n Documentation on Creating Custom Nodes
- Best practices for Handling API Credentials in n8n
This summary is based solely on static analysis of the provided source code and property definitions.