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 settings. Specifically, the "Instance" resource with the "Set Profile" operation allows updating the profile information of a WhatsApp instance. This is useful for customizing or changing the display name, status, or other profile-related details of the WhatsApp instance connected via the API.
Practical scenarios include:
- Automatically updating the WhatsApp instance profile based on business hours or campaigns.
- Changing profile information dynamically as part of a workflow that manages multiple WhatsApp instances.
- Keeping profile data consistent across different platforms by syncing updates through n8n.
Properties
| Name | Meaning |
|---|---|
| Additional Fields | Optional fields to customize the profile update request. Includes: |
| - Reply to Message ID: ID of message to reply to (string) | |
| - Delay (seconds): Delay before sending message (number) | |
| - Disable Link Preview: Whether to disable link previews in messages (boolean) | |
| - Mention Users: Comma-separated phone numbers to mention in the message (string) |
Note: For the "Set Profile" operation under the "Instance" resource, only the "Additional Fields" collection is available as input properties.
Output
The node outputs a JSON object containing the response from the Uazapi API after attempting to update the WhatsApp instance profile. The structure depends on the API's response but generally includes confirmation of the update or error details if the operation failed.
No binary data output is produced by this operation.
Example output JSON snippet:
{
"success": true,
"message": "Profile updated successfully",
"profile": {
// profile details returned by the API
}
}
Dependencies
- Requires an active Uazapi WhatsApp API account.
- Needs an API key credential and authentication token configured in n8n credentials for Uazapi.
- The node uses the Uazapi API base URL and instance ID from the credentials.
- Network access to the Uazapi service endpoint is required.
Troubleshooting
Common issues:
- Invalid or expired API token causing authentication failures.
- Incorrect instance ID leading to "instance not found" errors.
- Missing required fields in the additionalFields collection may cause the API to reject the request.
- Network connectivity problems preventing communication with the Uazapi server.
Error messages:
"Unauthorized"or"Invalid API token": Check and refresh your API credentials."Instance not found": Verify the instance ID is correct and active."Bad Request": Ensure all required parameters are correctly set and formatted.- Timeout or network errors: Confirm network connectivity and firewall settings.
To resolve errors, verify credentials, check parameter values, and consult Uazapi API documentation for specific error codes.
Links and References
- Uazapi Official Documentation (for detailed API usage and profile update parameters)
- n8n Documentation (for general node usage and credential setup)