Actions76
- Message Actions
- Chat Actions
- Contact Actions
- Group Actions
- Create
- List
- Get
- Delete
- Join
- Get Join Info
- Leave
- Get Picture
- Set Picture
- Delete Picture
- Update Subject
- Update Description
- Get Security Info Admin Only
- Set Security Info Admin Only
- Get Security Messages Admin Only
- Set Security Messages Admin Only
- Get Participants
- Add Participant
- Remove Participant
- Promote Admin
- Demote Admin
- Status Actions
- Channel Actions
- Poll Actions
- Profile Actions
- LID Actions
- File Actions
Contact → Get
AI-generatedOverview
This node enables interaction with WhatsApp via the Wappfy API, focusing on managing contacts among other resources. Specifically, the "Contact" resource with the "Get" operation allows users to retrieve detailed information about a specific WhatsApp contact by providing their Contact ID or phone number.
Common scenarios where this node is beneficial include:
- Fetching contact details for customer support automation.
- Integrating WhatsApp contact data into CRM systems.
- Verifying contact existence and retrieving profile information before sending messages.
Practical example:
- A user inputs a Contact ID (phone number or WhatsApp ID) to fetch the contact's profile details such as name, status, and profile picture URL, which can then be used in subsequent workflow steps.
Properties
| Name | Meaning |
|---|---|
| Contact ID | The unique identifier of the contact, which can be a Contact ID or phone number. This is required to specify which contact's details to retrieve. |
Output
The node outputs JSON data representing the contact's details as returned by the Wappfy API. This typically includes fields such as the contact's name, phone number, status/about, profile picture URL, and possibly other metadata related to the contact.
No binary data output is indicated for this operation.
Example output structure (simplified):
{
"id": "contact-id-or-phone",
"name": "Contact Name",
"status": "Contact status/about text",
"profilePictureUrl": "https://example.com/profile.jpg",
...
}
Dependencies
- Requires an active Wappfy API credential with a valid API key and instance name configured in n8n.
- The node makes HTTP requests to the Wappfy API endpoints using these credentials.
- Network access to the Wappfy API base URL is necessary.
Troubleshooting
Common issues:
- Invalid or missing Contact ID: The node requires a valid Contact ID or phone number; ensure this is correctly provided.
- Authentication errors: Verify that the API key credential is correctly set up and has sufficient permissions.
- Network connectivity problems: Ensure the n8n instance can reach the Wappfy API endpoint.
Error messages:
- Errors from the API will be returned as JSON error messages. If the node is set to continue on fail, these errors appear in the output JSON under an
errorfield. - Typical errors include "Contact not found" if the Contact ID does not exist, or "Unauthorized" if API credentials are invalid.
- Errors from the API will be returned as JSON error messages. If the node is set to continue on fail, these errors appear in the output JSON under an
Resolution tips:
- Double-check the Contact ID format.
- Confirm API credentials and instance name.
- Check network/firewall settings.
Links and References
- Wappfy API Documentation (general reference for API endpoints)
- WhatsApp Business API Overview (for understanding WhatsApp contact concepts)
This summary focuses exclusively on the "Contact" resource with the "Get" operation as requested.