WasenderAPI icon

WasenderAPI

Manage WasenderAPI sessions, messages, contacts, and groups

Actions53

Contact → Get Contact Picture

AI-generated

Overview

This node operation retrieves the profile picture of a specified contact in a WhatsApp session using the WasenderAPI. It is useful for scenarios where you need to display or process the contact's profile image, such as in customer support dashboards, contact management systems, or messaging applications.

Use Case Examples

  1. Fetching a contact's profile picture to display in a CRM system.
  2. Retrieving the profile image of a contact to use in a messaging app interface.

Properties

Name Meaning
Session Selects the WhatsApp session to use for the API request. It can be chosen from a list or specified by ID. This is optional if the session is provided in the input item.
Contact Specifies the contact whose profile picture is to be retrieved. It can be selected from a list or provided by the contact's JID (Jabber ID).
Options Additional request options such as retry behavior on failed requests and maximum retry attempts.

Output

Binary

The node outputs the contact's profile picture as binary data, allowing it to be used directly in workflows that handle images.

JSON

  • resourceType - Indicates the type of resource, here it will be 'contact'.
  • resourceId - The unique identifier (JID) of the contact.
  • pictureUrl - The URL of the contact's profile picture.
  • mimeType - The MIME type of the profile picture image.
  • fileName - The filename assigned to the profile picture image.

Dependencies

  • Requires a valid WhatsApp session and an API key credential for WasenderAPI to authenticate requests.

Troubleshooting

  • Common issues include invalid or missing session ID, incorrect contact JID, or network errors when fetching the picture.
  • Error messages may indicate missing image URL in the API response or failure to download the image binary data.
  • Ensure the session is active and the contact exists in the session's contact list.
  • Verify that the API credentials are correctly configured and have necessary permissions.

Discussion