Actions33
Overview
This node operation retrieves a picture from a WhatsApp conversation using the Quepasa API. It supports specifying the chat ID and an optional picture ID to check for updates. Users can choose to receive the picture data either as JSON or as binary data, which is useful for handling images directly within workflows. This operation is beneficial for automating the retrieval and processing of images from WhatsApp chats, such as for archiving, analysis, or forwarding images within an automation pipeline.
Use Case Examples
- Automatically download and save profile pictures or shared images from a WhatsApp group chat.
- Fetch the latest picture from a specific chat for processing or monitoring purposes.
- Retrieve images as binary data to integrate with other systems that require file inputs.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authentication to use, either parameters or predefined credentials. |
| BaseUrl | The base URL of the Quepasa API endpoint, required if using parameter-based authentication. |
| Token | The token of the WhatsApp bot used for authentication, required if using parameter-based authentication. |
| Chat ID | The destination conversation identifier, which can be a ChatId Group or any E164 phone number. |
| Picture ID | Optional picture ID used to check for updates in cached pictures. |
| Download Binary | Flag indicating whether to return the picture data in binary format. |
| Binary Property | The name of the binary property that will contain the file data if binary output is enabled. |
| File Name | The file name and extension for the binary file, auto-generated if not provided. |
Output
Binary
Contains the picture data as a binary file if 'Download Binary' is enabled.
JSON
chatid- The chat identifier from which the picture was retrieved.pictureId- The identifier of the picture retrieved, useful for caching or update checks.data- The picture data in JSON format if binary download is not enabled.
Dependencies
- Quepasa API, requiring either parameter-based or predefined token authentication.
Troubleshooting
- Authentication errors due to invalid or missing token or base URL. Ensure correct credentials are provided based on the selected authentication method.
- Errors in retrieving the picture if the chat ID is incorrect or the picture ID does not exist. Verify the chat ID and picture ID values.
- If binary download is enabled but the binary property name is incorrect or missing, the output file may not be created properly. Ensure the binary property name matches the expected value.