Actions55
- Message Actions
- Contact Actions
- Chat Actions
- Group Actions
- Queue Actions
- Account Actions
- Session Actions
- Session Control Actions
- Call Actions
Account → Set Webhook
AI-generatedOverview
This node integrates with the Maytapi WhatsApp Unofficial API, enabling automation and management of WhatsApp accounts, messages, contacts, groups, calls, and sessions. Specifically for the Account - Set Webhook operation, it allows users to configure a webhook URL on their Maytapi WhatsApp product account. This webhook URL is where WhatsApp events such as incoming messages, status updates, or other notifications will be sent in real-time.
Use cases include:
- Receiving WhatsApp message notifications directly into your workflow.
- Automating responses or processing based on incoming WhatsApp events.
- Integrating WhatsApp communication events with other systems via webhooks.
Example: Setting a webhook URL to your server endpoint (e.g., https://myserver.com/webhook) so that all WhatsApp events from your Maytapi account are pushed there for further processing.
Properties
| Name | Meaning |
|---|---|
| Phone ID Source | How to provide the Phone ID (used for most operations except Account resource): - From Credentials - Custom (enter manually) |
| Phone ID | The WhatsApp instance Phone ID (required if "Custom" Phone ID Source is selected). |
| Webhook URL | The URL where webhook events will be sent. This is required for the Account - Set Webhook operation. |
Note: For the Account - Set Webhook operation, only the Webhook URL property is relevant and required.
Output
The node outputs JSON data representing the response from the Maytapi API after setting the webhook. Typically, this includes success confirmation or error details returned by the API.
No binary data output is involved in this operation.
Example output JSON structure:
{
"success": true,
"message": "Webhook set successfully"
}
or in case of failure:
{
"error": "Invalid webhook URL"
}
Dependencies
- Requires an active Maytapi WhatsApp API product account.
- Requires an API key credential for authentication with Maytapi API.
- The node uses the Maytapi REST API endpoint
https://api.maytapi.com/api/setWebhook. - Proper network access to the specified webhook URL must be ensured for event delivery.
Troubleshooting
- Phone ID missing error: Although not applicable for Account resource operations, other resources require a valid Phone ID either from credentials or custom input.
- Invalid webhook URL: Ensure the webhook URL is a valid HTTPS endpoint accessible from the internet.
- API authentication errors: Verify that the API key credential is correctly configured and has necessary permissions.
- Network issues: The webhook URL must be reachable by Maytapi servers; firewall or DNS issues can prevent webhook delivery.
- Error responses from API: Check the exact error message returned in the node output JSON for clues and correct accordingly.