Actions39
- Chatbot Actions
- Contact Actions
- Message Actions
- Panel Actions
- Sequence Actions
- Session Actions
Overview
The "Get All Sequences" operation for the Sequence resource in the WTS Chat n8n node retrieves a list of sequences from the WTS API. This is useful for automation scenarios where you need to fetch, filter, or process marketing or communication sequences (such as drip campaigns or automated message flows) associated with contacts in your system.
Common use cases:
- Listing all available sequences for reporting or dashboarding.
- Filtering sequences by name, contact association, or creation/update dates.
- Integrating sequence data into other workflows, such as syncing with CRM systems or triggering actions based on sequence properties.
Example:
You might use this node to pull all sequences created after a certain date and then send a summary email, or to find all sequences associated with a specific contact for further processing.
Properties
Below are the input properties relevant to the "Get All Sequences" operation:
| Display Name | Type | Description |
|---|---|---|
| Name | String | Filter sequences by their name. |
| Contact ID | String | Filter sequences that include a specific contact. |
| CreatedAt.After | DateTime | Only return sequences created after this date/time. |
| CreatedAt.Before | DateTime | Only return sequences created before this date/time. |
| UpdatedAt.After | DateTime | Only return sequences updated after this date/time. |
| UpdatedAt.Before | DateTime | Only return sequences updated before this date/time. |
| Auto Pagination | Boolean | If enabled, automatically retrieve multiple pages of results. |
| Max Pages | Number | Maximum number of pages to retrieve when auto pagination is enabled (1–100). |
| Page Number | Number | The page number to retrieve (used if auto pagination is disabled). |
| Page Size | Number | Number of items per page (used if auto pagination is disabled; 1–100). |
| Order By | String | Field to sort the results by. |
| Order Direction | Options | Sort direction: Ascending or Descending. |
Output
The output will be an array of objects under the json field, each representing a sequence. The structure typically includes (but is not limited to):
{
"id": "string",
"name": "string",
"createdAt": "string (ISO date)",
"updatedAt": "string (ISO date)",
// ...other sequence-specific fields
}
- Each item in the output corresponds to a sequence matching the provided filters.
- The exact fields depend on the WTS API response but generally include identifiers, names, timestamps, and possibly additional metadata.
Dependencies
- External Service: Requires access to the WTS API.
- API Key: You must configure valid WTS API credentials (
wtsApi) in n8n. - n8n Configuration: Ensure the node has network access to
https://api.wts.chat.
Troubleshooting
Common Issues:
- Missing Credentials: If the API key is not set up, the node will fail to authenticate.
- Invalid Filters: Supplying invalid date formats or out-of-range values for pagination may result in errors or empty results.
- API Limits: Requesting too many pages or a large page size may hit API rate limits or timeouts.
Error Messages:
"NodeApiError: ...": Indicates an error returned from the WTS API or due to misconfiguration. Check the error message for details."Invalid date format": Ensure date/time fields follow the required format (e.g.,YYYY-MM-DD hh:mm)."Max Pages/Page Size out of range": Make sure these values are within allowed limits (1–100).
How to resolve:
- Double-check your API credentials.
- Validate all input parameters, especially date/time and pagination settings.
- Review the error message for hints about which parameter or configuration caused the issue.