Actions21
Overview
The "Send Text" operation of the DinastiAPI AI node enables sending plain text messages via WhatsApp to individual users, groups, newsletters, or LIDs. It supports advanced messaging features such as forwarding, replying to specific messages, and mentioning users or all group members. This node is particularly useful for automating communication workflows, customer support, marketing campaigns, or any scenario where programmatic WhatsApp messaging is needed.
Practical examples include:
- Sending personalized notifications or alerts to customers.
- Replying automatically to user inquiries with contextual references.
- Broadcasting announcements to groups or newsletters with mentions.
- Simulating typing presence to enhance user experience.
Properties
| Name | Meaning |
|---|---|
| Recipient | Phone number, Group ID (@g.us), Newsletter ID (@newsletter), or LID (@lid) to which the message will be sent. |
| Message | The text content of the message to send. |
| Additional Options | Collection of optional settings: |
| - Message ID | Custom identifier for the message; if not provided, it is auto-generated. |
| - Presence Simulation | Duration in milliseconds (0-30000) to simulate typing or recording presence indicator before sending the message. |
| - Message Duration | Duration in seconds for WhatsApp disappearing message feature. Options: No Expiration, 24 Hours, 7 Days, 90 Days. |
| - Link Preview | Whether to generate an automatic preview for URLs included in the text message (true/false). |
| - Context Information | Contextual metadata for the message including: |
| - Forward Message | Mark the message as forwarded (true/false). |
| - Mention All | Mention all group members (groups only) (true/false). |
| - Mention Specific Users | Comma-separated list of user JIDs to mention in the message. |
| - Reply To Message ID | ID of the message being replied to. |
| - Reply To Participant | JID of the original sender of the message being replied to (required for replies). |
Output
The node outputs a JSON object containing the response from the DinastiAPI after attempting to send the text message. This response typically includes status information about the message delivery, message IDs, and any metadata returned by the API.
If the node is used as a tool with response optimization enabled, the output may be truncated or structured to reduce token usage for AI processing, indicated by additional fields such as _aiOptimized and _truncated.
No binary data is produced by this operation.
Dependencies
- Requires an active connection to the DinastiAPI service with a valid API key credential configured in n8n.
- The node uses HTTP requests to communicate with the DinastiAPI endpoints.
- Proper network access to the DinastiAPI servers is necessary.
Troubleshooting
- Missing Required Fields: Ensure that the "Recipient" and "Message" fields are provided; otherwise, the node will throw errors.
- Invalid Recipient Format: The recipient must be a valid phone number or identifier with correct suffixes (
@s.whatsapp.net,@g.us, etc.). Incorrect formats may cause message sending failures. - Binary Property Not Found: Although not applicable for Send Text, other operations requiring binary data will error if the specified binary property is missing.
- API Errors: If the DinastiAPI returns errors (e.g., authentication failure, rate limits), these will be surfaced in the node's output. Verify API credentials and usage limits.
- Context Information Misconfiguration: When using reply or mention options, ensure that required fields like participant JID are correctly set to avoid message rejection.
Links and References
- DinastiAPI GitHub Repository
- WhatsApp Business API documentation (for general understanding of message types and context info)