Actions25
- Get Actions
- Message Actions
- Friend Actions
- Group Actions
- Tool Actions
Overview
This node operation allows adding a user to a Zalo group by specifying the group's ID and the user's phone number. It is useful in scenarios where you want to programmatically manage group memberships on Zalo, such as automating the addition of new members based on their phone numbers without requiring manual intervention.
Practical examples include:
- Automatically adding customers or clients to a support or community group after they register with their phone number.
- Managing event groups by adding participants via their phone numbers.
- Integrating with CRM systems to sync contacts into Zalo groups.
Properties
| Name | Meaning |
|---|---|
| Group Id | The unique identifier of the Zalo group to which the user will be added. |
| Phone Number | The phone number of the Zalo user to add to the specified group. |
Output
The node outputs JSON data representing the result of the add-user-to-group operation. This typically includes success status and any relevant metadata returned by the Zalo API about the operation. The output does not explicitly mention binary data, so it is assumed to be purely JSON.
Dependencies
- Requires an active connection to the Zalo platform's API.
- Needs appropriate API authentication credentials (e.g., an API key or token) configured in n8n to authorize requests.
- The node depends on internal SDK or HTTP request libraries to communicate with Zalo's backend services.
Troubleshooting
Common Issues
- Invalid Group Id: If the provided group ID does not exist or the authenticated user lacks permission, the operation will fail.
- Incorrect Phone Number Format: The phone number must be valid and registered on Zalo; otherwise, the user cannot be added.
- Authentication Errors: Missing or invalid API credentials will prevent the node from performing the action.
- API Rate Limits: Excessive requests may trigger rate limiting by Zalo's API.
Error Messages and Resolutions
- "Group not found" or "Access denied": Verify the group ID and ensure the API credentials have sufficient permissions.
- "User not found" or "Invalid phone number": Confirm the phone number is correct and the user exists on Zalo.
- "Unauthorized" or "Invalid token": Check that the API key/token is correctly set up in n8n credentials.
- Timeouts or network errors: Ensure stable internet connectivity and that Zalo's API endpoints are reachable.
Links and References
- Zalo Official API Documentation
- n8n Documentation - Creating Custom Nodes
- Zalo Group Management API Reference
Note: Internal credential names and specific implementation details are omitted for security and compliance.