Actions21
Overview
The "DinastiAPI AI" node integrates with the DinastiAPI service to interact with WhatsApp accounts and messaging features. It supports a wide range of operations such as sending various types of messages (text, images, documents, audio, video, locations, contacts, stickers, buttons, lists, polls, links, status updates), retrieving user or group information, checking if users have active WhatsApp accounts, downloading avatars, and more.
This node is particularly useful for automating WhatsApp communication workflows, including customer support, marketing campaigns, notifications, and AI-driven chatbots. For example, it can verify if a phone number is registered on WhatsApp before sending a message, send multimedia content dynamically, or fetch detailed user info for personalization.
The "Check User" operation specifically verifies whether given phone numbers correspond to active WhatsApp accounts, helping prevent errors when sending messages to invalid recipients.
Properties
| Name | Meaning |
|---|---|
| Phone Number | Phone number in international format (without +). Required for "Check User" and "Get User Info" operations. |
| Optimize Response | Whether to optimize the API response to reduce token usage and improve AI processing. |
| Max Response Length | Maximum number of characters in the response; longer responses will be truncated. |
| Include Only Essential Fields | Whether to include only essential fields in the response to reduce noise. |
| Response Format | How to format the response for optimal AI agent understanding. Options: - Optimized: Clean, structured response optimized for AI. - Raw: Complete raw API response. - Summary: Brief summary with key information only. |
Output
- The node outputs JSON data representing the response from the DinastiAPI endpoints corresponding to the selected operation.
- For the "Check User" operation, the output JSON contains verification results indicating whether the specified phone numbers have active WhatsApp accounts.
- If the "Optimize Response" option is enabled, the output may be truncated or simplified to reduce size and focus on essential information, marked with metadata flags like
_aiOptimizedand_truncated. - The node can also output binary data when fetching avatars if configured to save the avatar image as binary. In this case, the binary data contains the avatar image encoded in base64 along with MIME type and filename metadata.
Dependencies
- Requires an API key credential for authenticating with the DinastiAPI service.
- The node makes HTTP requests to DinastiAPI endpoints to perform operations.
- No additional external dependencies are required beyond the configured API credential.
- For avatar downloads saved as binary, the node performs an additional HTTP GET request to retrieve the image data.
Troubleshooting
- Binary Property Not Found: When using media sources set to "binary," if the specified binary property does not exist in the input data, the node throws an error indicating the missing property. Ensure the previous node provides the expected binary data under the correct property name.
- Unknown Operation Error: If an unsupported operation value is provided, the node throws an "Unknown operation" error. Verify that the operation parameter is correctly set to one of the supported options.
- Avatar Not Found: When saving avatars as binary, if no avatar URL is returned by the API, the node outputs an error message stating "No avatar found or user has no avatar."
- API Request Failures: Network issues, invalid credentials, or API limits may cause request failures. Check API key validity and network connectivity.
- Response Optimization Issues: If response optimization is enabled but the response structure changes unexpectedly, the node falls back to returning the full raw response.
Links and References
- DinastiAPI GitHub Repository - Official documentation and source code for the DinastiAPI service.