WTS Chat icon

WTS Chat

Get data from Wts API

Actions39

Overview

The "Get Contacts By Sequence" operation in the WTS Chat node retrieves all contacts associated with a specific sequence identified by its Sequence ID. This node interacts with the WTS API to fetch contact data linked to marketing or communication sequences, which are typically used for automated messaging campaigns or customer journey workflows.

This operation is beneficial when you want to:

  • Extract all contacts currently enrolled in a particular sequence.
  • Analyze or export contact lists tied to specific campaign sequences.
  • Automate follow-up actions based on sequence membership.

Example use case:
A marketing automation workflow where you need to pull all contacts subscribed to a welcome email sequence to send them a personalized offer or update their status in a CRM system.

Properties

Name Meaning
Sequence ID The unique identifier of the sequence whose contacts you want to retrieve. Must be provided as a string.

Output

The output is an array of JSON objects, each representing a contact associated with the specified sequence. Each JSON object contains the contact's details as returned by the WTS API.

  • The json field includes contact information such as contact ID, phone number, name, and other metadata related to the contact within the sequence.
  • No binary data output is involved in this operation.

Dependencies

  • Requires an active connection to the WTS 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

  • Error: "SequenceID is empty!"
    Occurs if the Sequence ID property is not set or is an empty string. Ensure that the Sequence ID is correctly provided.

  • API errors (e.g., network issues, invalid API key)
    These will throw errors wrapped as NodeApiError. Verify that the API key is valid and that the WTS API service is reachable.

  • Rate limiting or timeout errors
    If retrieving contacts from very large sequences, consider handling pagination or adding delays between requests.

Links and References

Discussion