Actions20
- Message Actions
- Contact Actions
- Ticket Actions
- Session Actions
- Opportunity Actions
Overview
This node integrates with a WhatsApp API to manage WhatsApp sessions and send messages. Specifically, the "Session - Start" operation initiates an existing WhatsApp session by its ID. This is useful when you want to programmatically start a WhatsApp session that has been previously created but is currently inactive or disconnected.
Practical scenarios include:
- Automatically starting a WhatsApp session after deployment or system restart.
- Resuming communication channels without manual intervention.
- Managing multiple WhatsApp sessions in an automated workflow.
Properties
| Name | Meaning |
|---|---|
| WhatsApp ID | The numeric identifier of the WhatsApp session to start. This ID corresponds to a specific WhatsApp session instance managed by the API. |
Output
The node outputs JSON data representing the response from the WhatsApp API after attempting to start the session. This typically includes status information about the session start request, such as success confirmation or error details.
No binary data output is produced by this operation.
Example output structure (simplified):
{
"status": "success",
"message": "Session started successfully",
"sessionId": 1
}
Dependencies
- Requires an API key credential for authenticating with the WhatsApp API service.
- The node uses a base URL and instance ID configured in the credentials to construct API requests.
- The WhatsApp API must support session management endpoints such as
/startSession.
Troubleshooting
Common issues:
- Invalid or incorrect WhatsApp ID: Ensure the WhatsApp ID provided matches an existing session.
- Authentication failures: Verify that the API key credential is valid and has necessary permissions.
- Network or connectivity errors: Confirm that the base URL is reachable and the API service is operational.
Error messages:
"Unknown error occurred": Generic catch-all; check network, credentials, and input parameters.- API-specific error responses will be returned in the JSON output; review these for detailed diagnostics.
Resolution tips:
- Double-check the WhatsApp ID input.
- Validate API credentials and refresh if expired.
- Review API documentation for any changes in endpoint paths or required parameters.
Links and References
- WhatsApp Business API Documentation
- n8n HTTP Request Node Documentation
- Your WhatsApp API provider's official docs for session management endpoints (refer to your service provider).