Actions39
- Chatbot Actions
- Contact Actions
- Message Actions
- Panel Actions
- Sequence Actions
- Session Actions
Overview
This node interacts with the WTS Chat API to manage contacts, including retrieving contact information by phone number. The "Get By Phone" operation under the "Contact" resource fetches a contact's details using their phone number. This is useful in scenarios where you have a phone number and want to retrieve associated contact data, such as tags or custom fields, for further processing or automation.
Practical examples:
- Automatically fetching customer details when a phone number is received from an external source.
- Enriching workflows by pulling contact metadata based on phone numbers collected from forms or messages.
- Integrating with CRM systems to synchronize contact information using phone numbers as identifiers.
Properties
Name | Meaning |
---|---|
Phone Number | The phone number of the contact to retrieve. |
Include Details | Optional additional details to include in the response. Options: Tags, CustomFields. |
Output
The node outputs JSON data representing the contact information retrieved by phone number. The structure includes standard contact fields and optionally includes detailed data such as tags and custom fields if requested.
If binary data were involved (not applicable here), it would represent files or media related to the contact, but this operation only returns JSON contact data.
Dependencies
- Requires an API key credential for authenticating with the WTS Chat API.
- The node uses internal services (
WtsCoreService
) to perform API calls. - Network access to
https://api.wts.chat
is required.
Troubleshooting
- Empty or invalid phone number: Ensure the phone number parameter is correctly filled; otherwise, the API call will fail.
- API authentication errors: Verify that the API key credential is valid and has necessary permissions.
- No contact found: If no contact matches the phone number, the node may return an error or empty result depending on the API response.
- Include Details option misuse: Selecting unsupported options or incorrect formatting might cause unexpected results.
Common error messages:
- Errors thrown by the API are wrapped and rethrown as node errors with descriptive messages.
- "Invalid email!" error is unrelated here but appears in other operations; ensure input validation is correct in your workflow.
Links and References
- WTS Chat API Documentation (hypothetical link)
- n8n documentation on Creating Custom Nodes
- General info on handling contacts and phone numbers in automation workflows