Actions83
- Instances Actions
- Client Actions
- Message Actions
- Chat Actions
- Contact Actions
- Number Actions
- Group Actions
- Channel Actions
- Label Actions
- Story Actions
Overview
This node interacts with the WaAPI API to retrieve contact information. Specifically, the "Get Contacts" operation fetches details about a contact by its unique instance ID. This is useful in scenarios where you need to access or synchronize contact data from the WaAPI service within your workflows, such as fetching user profiles, managing contact lists, or integrating contact data into other systems.
Properties
| Name | Meaning |
|---|---|
| Id | The unique instance ID of the contact to retrieve. This is a required numeric identifier used to specify which contact's details to fetch. |
Output
The node outputs JSON data representing the contact information retrieved from the WaAPI API. The structure typically includes all relevant fields of the contact as defined by the API response, such as name, phone number, email, and other metadata associated with the contact.
If the API supports binary data for contacts (e.g., profile pictures), the node would include this in the binary output field; however, based on the provided code and properties, the primary output is JSON-formatted contact data.
Dependencies
- Requires an active connection to the WaAPI API.
- Needs an API authentication token configured in n8n credentials to authorize requests.
- The node uses the base URL
https://waapi.app/api/v1for API calls. - The request headers expect and send JSON content (
Accept: application/json,Content-Type: application/json).
Troubleshooting
- Missing or invalid Id: Since the Id property is required, omitting it or providing an invalid value will cause errors. Ensure the Id is a valid number corresponding to an existing contact.
- Authentication errors: If the API key or token is missing or incorrect, the node will fail to authenticate. Verify that the API credential is correctly set up in n8n.
- Network issues: Connectivity problems to
https://waapi.app/api/v1can cause timeouts or failures. Check network access and proxy settings if applicable. - API changes: If the WaAPI API changes its endpoints or response formats, the node might not work as expected until updated.
Links and References
- WaAPI Official Website
- WaAPI API Documentation (assumed typical location; verify actual docs URL)