MegaAPI icon

MegaAPI

Interact with MegaAPI WhatsApp service

Actions29

Overview

The node interacts with the MegaAPI WhatsApp service, specifically for managing webhook configurations when using the Webhook resource with the Get Webhook operation. This operation retrieves the current webhook configuration of your WhatsApp instance.

This is useful in scenarios where you want to verify or audit the webhook URL and settings currently active on your WhatsApp integration. For example, before updating webhook URLs or enabling/disabling notifications, you might want to fetch the existing configuration to confirm its state.

Practical examples:

  • Checking which webhook URL is currently set for receiving WhatsApp event notifications.
  • Verifying if webhook notifications are enabled or disabled.
  • Auditing webhook settings as part of a monitoring workflow.

Properties

Name Meaning
Information 🔗 This will retrieve the current webhook configuration for your WhatsApp instance

Note: The "Information" property here is a notice type used to inform users about the operation; it does not require input.

Output

The output JSON contains the current webhook configuration details retrieved from the WhatsApp instance via MegaAPI. This typically includes fields such as:

  • The webhook URL currently configured.
  • Status flags indicating whether webhook notifications are enabled or disabled.
  • Possibly other metadata related to webhook setup.

The exact structure depends on the API response but generally provides all relevant webhook configuration data.

No binary data output is expected from this operation.

Dependencies

  • Requires an API key credential for authenticating with the MegaAPI WhatsApp service.
  • The node uses the base URL and token from the credentials to make authenticated requests.
  • Proper configuration of the WhatsApp instance within MegaAPI is necessary for webhook management.

Troubleshooting

  • Common issues:

    • Invalid or expired API authentication token may cause authorization errors.
    • Incorrect or missing WhatsApp instance setup can lead to empty or error responses.
    • Network connectivity problems between n8n and MegaAPI endpoint.

  • Error messages:

    • Unknown webhook operation: getWebhook — indicates a misconfiguration or typo in the operation parameter.
    • Authorization errors usually mention invalid credentials or token issues.

  • Resolutions:

    • Verify that the API key credential is correctly set and valid.
    • Confirm the WhatsApp instance is properly configured in MegaAPI.
    • Check network access and firewall rules allowing communication with the MegaAPI host.

Links and References

Discussion