WTS Chat

Overview

This node interacts with a messaging and CRM platform's API to manage sequences of contacts. Specifically, the "Remove Contacts To Sequence" operation allows users to remove one or more 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 campaigns where contacts are organized into sequences.
• Removing contacts who have opted out or should no longer receive messages in a particular sequence.
• Automating cleanup or updates of contact lists within sequences based on external triggers or workflows.

Practical example:

• A user wants to remove multiple contacts from a promotional message sequence after they unsubscribe. They provide the sequence ID and a list of contact phone numbers or IDs to be removed, automating the update without manual intervention.

Properties

Output

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

No binary data output is involved in this operation.

Example output structure (conceptual):

{
  "json": {
    "success": true,
    "removedContacts": [
      "contactId1",
      "contactId2"
    ],
    "sequenceId": "sequenceIdValue"
  }
}

Dependencies

• Requires an active connection to the external messaging/CRM platform via an API key credential.
• The node uses the platform's API endpoint for sequences to perform contact removals.
• Proper configuration of the API key credential in n8n is necessary for authentication.

Troubleshooting

• Missing Sequence ID: If the sequence ID is empty or not provided, the node will throw an error indicating that the SequenceID field must be filled.
• No Contacts Provided: If neither contact IDs nor phone numbers 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., invalid sequence ID, unauthorized access) will be surfaced as errors. Check the API key validity and permissions.
• Invalid Input Format: Ensure that phone numbers and contact IDs are provided in the correct format and as arrays when multiple values are used.

Links and References

• Refer to the external messaging/CRM platform's API documentation for sequences management and contact operations.
• Consult n8n documentation on how to configure API key credentials and use custom nodes.