Actions38
- Chatbot Actions
- Contact Actions
- Message Actions
- Panel Actions
- Sequence Actions
- Session Actions
Overview
The node integrates with the WTS Chat API to manage sequences of contacts for messaging automation. Specifically, the Add Contact To Sequence operation allows users to add a single contact to a specified sequence by providing either the contact's ID or phone number. This is useful in scenarios where you want to enroll a contact into an automated message sequence or campaign.
Practical examples include:
- Adding a new lead or customer to a drip marketing sequence.
- Enrolling a contact who just signed up on your platform into a welcome message sequence.
- Automatically adding contacts from other workflows into engagement sequences.
Properties
| Name | Meaning |
|---|---|
| Sequence ID | The unique identifier of the sequence to which the contact will be added. |
| Contact ID | The unique identifier of the contact to add to the sequence. Optional if Phone Number is provided. |
| Phone Number | The phone number of the contact to add to the sequence. Optional if Contact ID is provided. |
Note: At least one of Contact ID or Phone Number must be provided to identify the contact.
Output
The output is a JSON object representing the result of the add-contact-to-sequence API call. It typically contains confirmation details about the contact being added to the sequence, such as success status and any relevant metadata returned by the API.
No binary data output is involved in this operation.
Example output structure (conceptual):
{
"success": true,
"sequenceId": "string",
"contactId": "string",
"message": "Contact added to sequence successfully"
}
Dependencies
- Requires an active connection to the WTS Chat API.
- An API key credential for authenticating requests to the WTS Chat service must be configured in n8n.
- The node depends on internal services (
WtsChatService) that handle API calls.
Troubleshooting
Error: "Add a contact either by ID or phone number"
Occurs if neither Contact ID nor Phone Number is provided.
Resolution: Provide at least one identifier for the contact.API Authentication Errors
If the API key is missing or invalid, the node will throw authentication errors.
Resolution: Ensure the API key credential is correctly set up in n8n.Invalid Sequence ID
If the sequence ID does not exist or is incorrect, the API may return an error.
Resolution: Verify the sequence ID is correct and exists in the WTS Chat system.Network or API Downtime
Temporary network issues or API downtime can cause request failures.
Resolution: Retry after some time or check the WTS Chat service status.
Links and References
- WTS Chat API Documentation (general reference URL from code)
- n8n documentation on Creating Custom Nodes
- Best practices for managing sequences and contacts in messaging platforms (varies by provider)
This summary is based solely on static analysis of the provided source code and property definitions.