Wappfy icon

Wappfy

Interact with WhatsApp through Wappfy API

Status → Send Voice

AI-generated

Overview

This node enables sending a voice status update on WhatsApp via the Wappfy API. It allows users to upload a voice message either by providing a direct URL to the media file or by supplying the Base64-encoded data of the audio. This is useful for automating status updates with voice notes, such as sharing quick audio announcements, reminders, or greetings with your WhatsApp contacts.

Practical examples include:

  • Automatically posting a daily voice status update.
  • Sharing voice memos as status updates in marketing campaigns.
  • Broadcasting voice alerts or notifications to selected contacts.

Properties

Name Meaning
Media Source Source of the media file; options are: URL (provide a direct link) or Base64 (encoded data).
File URL The URL of the voice file to send (required if Media Source is URL).
Base64 Data Base64 encoded voice file data (required if Media Source is Base64).
File Name Name of the voice file (used when Media Source is Base64; default is "file").
MIME Type MIME type of the voice file (e.g., audio/mpeg, audio/ogg) - required.

Output

The node outputs JSON data representing the response from the Wappfy API after attempting to send the voice status. The structure typically includes details about the sent status message, such as message ID and status confirmation.

If the operation fails, the output JSON will contain an error message describing the issue.

The node does not output binary data directly.

Dependencies

  • Requires an active Wappfy API account with valid credentials including:

    • Base URL of the Wappfy API.
    • Instance name identifying the WhatsApp session.
    • An API key credential for authentication.
  • The node makes HTTP POST requests to the Wappfy API endpoints to send voice statuses.

  • Proper configuration of the Wappfy API credentials in n8n is necessary.

Troubleshooting

  • Common issues:

    • Incorrect or missing API credentials will cause authentication failures.
    • Providing an invalid or inaccessible file URL will result in errors.
    • Supplying improperly formatted Base64 data may cause the API to reject the request.
    • Missing required properties like MIME type or file source will prevent successful execution.
  • Error messages:

    • Authentication errors indicate problems with the API key or instance name.
    • HTTP 400 errors often mean missing or invalid parameters.
    • Network errors suggest connectivity issues with the Wappfy API endpoint.
  • Resolutions:

    • Verify API credentials and instance name correctness.
    • Ensure URLs are publicly accessible and correctly formatted.
    • Validate Base64 encoding of the audio file.
    • Fill all required fields according to the property definitions.

Links and References


Note: This summary is based solely on static analysis of the provided source code and property definitions.

Discussion