WTS ChatInstall

Overview

This node interacts with the "Sequence" resource of the WTS Chat API, specifically focusing on managing contacts within sequences. The "Remove Contacts To Sequence" operation allows users to remove one or multiple contacts from a specified sequence by providing either their contact IDs or phone numbers.

Common scenarios where this node is beneficial include:

• Managing marketing or communication sequences by dynamically removing contacts who have opted out or no longer should receive messages.
• Cleaning up sequences to maintain accurate targeting lists.
• Automating contact management workflows where contacts are removed from sequences based on external triggers or conditions.

For example, if you have a sequence for a promotional campaign and some contacts unsubscribe, you can use this node to remove those contacts from the sequence automatically by specifying their phone numbers or contact IDs.

Properties

Output

The output of this operation is a JSON object containing the response from the WTS Chat API after attempting to remove the specified contacts from the sequence. This typically includes confirmation of removal or details about the updated sequence state.

The structure is:

[
  {
    "json": {
      // API response data confirming removal or status
    }
  }
]

No binary data output is produced by 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.chat is necessary.

Troubleshooting

• Missing Sequence ID: If the "Sequence ID" is empty or invalid, the node will throw an error indicating that the SequenceID field must be filled.
• No Contacts Provided: If neither phone numbers nor contact IDs are provided, the node throws an error instructing to add at least one contact identifier.
• API Errors: Any errors returned by the WTS Chat API (e.g., invalid IDs, permission issues) will be surfaced as node errors. Check the API response message for details.
• Rate Limiting / Delays: The node includes a delay mechanism when processing multiple items to avoid hitting rate limits. If you experience delays, consider adjusting your workflow accordingly.
• Invalid Phone Number Format: Ensure phone numbers are correctly formatted as expected by the API to prevent rejection.

Links and References

• WTS Chat API Documentation (general reference)
• n8n documentation on Creating Custom Nodes
• Best practices for managing sequences and contacts in messaging platforms (refer to your platform's official guides)

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