Actions18
- Contact Actions
- Message Actions
- Conversation Actions
- Note Actions
- File Actions
Overview
The node integrates with the Superchat API to search for contacts based on specific fields. It allows users to find a contact by providing a search criterion such as email address, phone number, or Instagram handle. This is useful in scenarios where you want to retrieve contact details dynamically within an automation workflow, for example, to personalize messages, update contact records, or trigger actions based on contact information.
Practical examples:
- Searching for a contact by their email address to fetch their profile before sending a targeted email campaign.
- Looking up a contact using their phone number to verify if they exist in the system before initiating a call or SMS.
- Finding a contact via their Instagram handle to integrate social media interactions into your CRM workflows.
Properties
| Name | Meaning |
|---|---|
| Search Field | The field used to search the contact. Options: Email Address, Phone Number, Instagram Handle |
| Value | The actual value to search for in the selected field (e.g., an email address or phone number) |
Output
The node outputs an array of JSON objects representing the contacts that match the search criteria. Each object contains the contact's data as returned by the Superchat API, which typically includes identifiers and contact details relevant to the searched field.
If the node supports binary data output, it would be related to contact attachments or files, but this operation focuses solely on JSON data representing contact information.
Dependencies
- Requires an active connection to the Superchat API.
- Needs an API authentication token configured in n8n credentials to authorize requests.
- No additional external dependencies are indicated.
Troubleshooting
- No results found: If the search returns an empty array, verify that the search field and value are correct and that the contact exists in Superchat.
- Authentication errors: Ensure the API key or token credential is valid and has sufficient permissions.
- Invalid input errors: Confirm that the "Value" property is not empty and matches the expected format for the chosen search field (e.g., valid email format).
- API rate limits: If many searches are performed rapidly, the API might throttle requests; consider adding delays or handling retries.