Actions37
- Message Actions
- Media Actions
- Contact Actions
- Group Actions
- Instance Actions
- Webhook Actions
Overview
This node integrates with the Uazapi WhatsApp API, enabling users to manage and automate WhatsApp messaging and instance operations within n8n workflows. Specifically, the "Restart Instance" operation under the "Instance" resource allows restarting a WhatsApp instance remotely via the API.
Use cases include:
- Automatically restarting a WhatsApp instance when it becomes unresponsive or encounters errors.
- Scheduling periodic restarts for maintenance or performance optimization.
- Integrating restart commands into broader automation workflows that monitor system health.
Example: After detecting connection issues in your WhatsApp integration, trigger this node to restart the instance and restore connectivity without manual intervention.
Properties
| Name | Meaning |
|---|---|
| Additional Fields | Optional extra parameters for the request. Includes: |
| - Reply to Message ID: ID of message to reply to | |
| - Delay (seconds): Delay before sending message | |
| - Disable Link Preview: Disable link previews in messages | |
| - Mention Users: Comma-separated phone numbers to mention |
Note: For the "Restart Instance" operation, only the "Additional Fields" collection is available as input properties, but typically no additional fields are required.
Output
The node outputs a JSON object containing the response from the Uazapi API after attempting to restart the WhatsApp instance. The structure generally includes status information about the restart request.
Output example (conceptual):
{
"status": "success",
"message": "Instance restart initiated"
}
No binary data output is produced by this operation.
Dependencies
Requires an active Uazapi API credential configured in n8n, including:
- API key credential for authentication.
- API URL endpoint.
- API token for authorization.
- Instance ID identifying the WhatsApp instance to restart.
The node sends requests through a proxy service hosted at
https://n8ntools.io/api/v1/proxy/uazapi.
Troubleshooting
Common Issues:
- Invalid or expired API credentials may cause authentication failures.
- Incorrect instance ID will result in failure to locate the WhatsApp instance.
- Network connectivity problems can prevent the API call from succeeding.
Error Messages:
"Unknown resource: instance": Indicates the resource parameter was not set correctly; ensure "Instance" is selected.- API error responses with HTTP status codes indicating unauthorized access or bad requests should be checked against credential validity and parameter correctness.
Resolution Tips:
- Verify all credential details are correct and up to date.
- Confirm the instance ID matches the target WhatsApp instance.
- Check network access and proxy availability.
- Use the node's "Continue On Fail" option to handle errors gracefully in workflows.
Links and References
- Uazapi Official Documentation (for detailed API usage)
- n8n Documentation on Credentials
- WhatsApp Business API Overview