WTS Chat

Overview

The "Remove Contact To Sequence" operation in the Sequence resource allows users to remove a contact from a specific sequence in the WTS Chat system. This is useful for managing contact lists within automated messaging or marketing sequences, ensuring that contacts no longer relevant or who opted out are excluded from ongoing communications.

Typical use cases include:

• Removing a contact who unsubscribed from a campaign.
• Cleaning up sequences by removing inactive or invalid contacts.
• Managing contact lifecycle dynamically based on user behavior or external triggers.

For example, if you have an automated onboarding sequence and a user requests to stop receiving messages, this operation can be used to remove their contact ID or phone number from that sequence.

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 node outputs a JSON object representing the result of the removal operation. This typically includes confirmation details such as success status or any metadata returned by the API about the updated sequence or contact removal.

No binary data output is involved in this operation.

Example output structure (conceptual):

{
  "success": true,
  "sequenceId": "string",
  "contactRemoved": {
    "contactId": "string",
    "phoneNumber": "string"
  }
}

Dependencies

• Requires an API key credential for authenticating with the WTS Chat API.
• The node depends on the WTS Chat service endpoints to perform sequence and contact management.
• No additional environment variables are explicitly required beyond the API key credential.

Troubleshooting

• Missing Sequence ID: If the Sequence ID is empty or not provided, the node will throw an error indicating the field must be filled.
• Missing Contact Identification: If neither Contact ID nor Phone Number is provided, the node throws an error instructing to add at least one.
• API Errors: Any issues communicating with the WTS Chat API (e.g., invalid API key, network errors) will result in an error with details from the API response.
• Rate Limiting: Since the node includes a delay when processing multiple items, hitting rate limits might still occur if many removals happen rapidly; consider batching or throttling accordingly.

To resolve common errors:

• Ensure all required fields (Sequence ID and either Contact ID or Phone Number) are correctly set.
• Verify the API key credential is valid and has necessary permissions.
• Check network connectivity and API endpoint availability.

Links and References

• WTS Chat API Documentation (general reference for API endpoints)
• n8n documentation on Creating Custom Nodes
• Best practices for managing sequences and contacts in messaging platforms (varies by platform)

---

This summary is based solely on static analysis of the provided source code and property definitions.