Actions148
- Send messages Actions
- Outbound Messages Actions
- WhatsApp Numbers Actions
- Groups Actions
- Channels Actions
- Chats Actions
- Chat Contacts Actions
- Chat Messages Actions
- Chat Files Actions
- Team Actions
- Labels Actions
- Departments Actions
- Files Actions
- Quick replies Actions
- Queue Actions
- WhatsApp session Actions
- WhatsApp profile Actions
- Business catalog Actions
- Campaigns Actions
- Meeting Links Actions
- User Status Actions
- Webhooks Actions
- Other Actions
WhatsApp session → Start session
AI-generatedOverview
This node integrates with the WaliChat WhatsApp API to manage WhatsApp sessions. Specifically, the "Start session" operation under the "WhatsApp session" resource initiates a session for a selected WhatsApp number (device). This is useful when you want to programmatically start or activate a WhatsApp session linked to a particular phone number managed by WaliChat.
Common scenarios include:
- Automating the activation of WhatsApp sessions before sending messages.
- Managing multiple WhatsApp numbers and ensuring their sessions are active.
- Waiting for the session to be fully available before proceeding with further actions, which can help in workflows that depend on an active session.
Example: You have several WhatsApp numbers connected via WaliChat and want to ensure a specific number's session is started and ready before sending bulk messages or handling incoming chats.
Properties
| Name | Meaning |
|---|---|
| WhatsApp Number | The ID of the WhatsApp number (device) for which the session should be started. |
| Wait For Session | Whether to wait for the device session to become available before continuing (may delay up to 90 seconds). |
Output
The node outputs JSON data representing the result of starting the WhatsApp session. This typically includes status information about the session initiation process, such as success confirmation or session details returned from the WaliChat API.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential for authenticating with the WaliChat WhatsApp API.
- The node depends on the WaliChat service being accessible and properly configured.
- The "WhatsApp Number" property relies on dynamically loaded options, which means the node fetches available devices from WaliChat before execution.
Troubleshooting
- Session Start Delay: If "Wait For Session" is enabled, the node may take up to 90 seconds to respond. Users should be aware of this potential delay in their workflow timing.
- Invalid WhatsApp Number: Selecting a non-existent or inactive WhatsApp number/device will likely cause errors. Ensure the device ID is valid and active.
- API Authentication Errors: Missing or invalid API keys will prevent the node from communicating with WaliChat. Verify credentials are correctly set.
- Network Issues: Connectivity problems with the WaliChat API endpoint can cause failures. Check network access and API availability.
- Error Messages: Errors thrown by the node will contain messages from the WaliChat API or internal validation. Enabling "Continue On Fail" allows workflows to handle these gracefully.
Links and References
- WaliChat Official API Documentation (example placeholder link)
- n8n Documentation on Creating Custom Nodes
- General WhatsApp Business API concepts for context on sessions and devices.