Actions20
- Message Actions
- Contact Actions
- Ticket Actions
- Session Actions
- Opportunity Actions
Overview
This node integrates with a WhatsApp API to send messages and manage related entities such as contacts, tickets, sessions, and opportunities. Specifically, the Send File URL operation under the Message resource allows users to send a file to a WhatsApp number by providing a publicly accessible URL of the media file.
Common scenarios for this operation include:
- Sending images, documents, or other media files hosted online directly to customers via WhatsApp.
- Automating customer support by attaching relevant files (e.g., invoices, manuals) in conversations.
- Sharing promotional materials or product catalogs through WhatsApp messages.
Example: A business wants to send a PDF brochure to a client’s WhatsApp number automatically when they request it on a website form. The node can send the brochure file URL along with a message text to the client’s WhatsApp.
Properties
| Name | Meaning |
|---|---|
| Phone Number | WhatsApp number of the recipient in international format without "+" (e.g., 5511999999999). |
| Message Text | Text content accompanying the file being sent. |
| External Key | Unique system key to identify the message transaction. |
| Close Ticket | Boolean flag indicating whether to close the associated ticket after sending the message. |
| Media URL | Publicly accessible URL of the file to be sent via WhatsApp. |
Output
The node outputs an array of JSON objects corresponding to each input item processed. Each output JSON contains the response from the WhatsApp API after attempting to send the file URL message. This typically includes status information about the message delivery or any errors returned by the API.
No binary data is output by this operation; all responses are JSON-formatted metadata about the message sending process.
Dependencies
- Requires configuration of an API authentication credential (an API key or token) for the WhatsApp API service.
- The node uses the base URL and instance ID from these credentials to construct API requests.
- The media file must be accessible via the provided URL without authentication restrictions.
Troubleshooting
- Invalid Phone Number Format: Ensure the phone number is in the correct international format without "+" or spaces (e.g., 5511999999999).
- Media URL Inaccessible: The file URL must be publicly reachable. If the API returns an error about the media, verify the URL is correct and accessible.
- API Authentication Errors: Check that the API credentials are valid and have not expired.
- Ticket Closure Issues: If the "Close Ticket" option is enabled but the ticket does not close, verify that the external system supports this feature and that the externalKey matches an existing ticket.
- Error Messages: The node will return error details in the output JSON if the API call fails. Review these messages to identify issues such as invalid parameters or server errors.