Actions50
- Account Actions
- Call Actions
- Chat Actions
- Contact Actions
- Group Actions
- Instance Actions
- Media Actions
- Message Actions
- Session Actions
- User Actions
Overview
This node interacts with the WSAPI WhatsApp API to manage various WhatsApp-related resources. Specifically, for the Account resource and the Set Presence operation, it allows users to set their WhatsApp presence status visibility. This means you can programmatically control whether your WhatsApp account appears online or offline to your contacts.
Common scenarios where this is useful:
- Automatically setting your WhatsApp status to "Unavailable" during non-working hours.
- Indicating availability dynamically based on external triggers or workflows.
- Integrating WhatsApp presence status changes into broader communication automation.
Practical example:
A customer support workflow could set the WhatsApp presence to "Available" when agents are online and switch to "Unavailable" outside business hours, ensuring customers see accurate availability.
Properties
| Name | Meaning |
|---|---|
| Status | Set your WhatsApp presence status visibility. Options: - Available: show online status to contacts - Unavailable: appear offline |
Output
The node outputs JSON data representing the result of the presence status update operation. The exact structure depends on the WSAPI response but typically includes confirmation of the status change or error details if the operation failed.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential for authenticating with the WSAPI WhatsApp API.
- The node expects a base URL configured in the credentials to connect to the WSAPI endpoint.
- No other external dependencies are required.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication failures.
- Incorrect base URL configuration may lead to connection errors.
- Providing unsupported status values will result in validation errors.
Error messages:
"The resource "account" is not known!"— indicates an invalid resource selection; ensure "Account" is selected."The operation "setPresence" is not implemented yet!"— suggests the operation name might be misspelled or not supported; verify operation choice.- Network or API errors will return messages from the WSAPI; check credentials and network connectivity.
Resolution tips:
- Double-check API credentials and base URL settings.
- Use only the allowed status options ("Available" or "Unavailable").
- Enable "Continue On Fail" in the node settings to handle errors gracefully in workflows.
Links and References
- WSAPI WhatsApp API Documentation (replace with actual URL)
- n8n Documentation on Creating Custom Nodes
- WhatsApp Business API Overview