Wasapi

Integration oficial of Wasapi API for n8n

Actions19

Agent Actions
- Change Chat Status or Transfer
Campaign Actions
- Get By UUID
Contact Actions
Custom Field Actions
Label Actions
WhatsApp Actions

Overview

This node integrates with the Wasapi API to manage WhatsApp chat conversations, specifically allowing users to change the status of a chat or transfer it to another agent. It is useful in customer support or sales scenarios where conversations need to be tracked by status (open, hold, closed) or reassigned to different agents for handling.

Practical examples:

Marking a conversation as "hold" when waiting for customer response.
Closing a conversation once the issue is resolved.
Transferring an active chat to a specialized agent with a note explaining the reason.

Properties

Name	Meaning
Phone Wasapi Name or ID	Select the phone number associated with your Wasapi account from a list or specify its ID via expression.
WhatsApp ID	The customer's phone number in international format without the "+" sign (e.g., 573203294920).
Status	The chat status to assign: Open, Hold, or Closed.
(Optional) Agent	When setting status to Open, optionally select the agent to assign the conversation to.
(Optional) Message	A note to include if transferring the chat, providing context or instructions.

Output

The node outputs JSON data representing the result of the status change or transfer operation on the WhatsApp conversation. This typically includes confirmation details such as updated chat status, assigned agent information, and any messages sent during the transfer. The node does not output binary data.

Dependencies

Requires an API key credential for authenticating with the Wasapi API.
Needs proper configuration of the Wasapi API base URL (defaulted to https://api-ws.wasapi.io/api/v1).
Uses helper methods to load options dynamically, such as available WhatsApp numbers and agents.

Troubleshooting

Common issues:
- Invalid or missing WhatsApp ID format can cause errors; ensure the number includes country code without "+".
- Assigning an agent when status is not "open" may be ignored or cause unexpected behavior.
- Network or authentication failures with the Wasapi API will prevent execution.
Error messages:
- "Resource 'agents' with operation 'assignAgent' is not supported" indicates a mismatch in resource-operation parameters.
- Authentication errors suggest checking the API key credential validity.
- Validation errors on input properties usually mean required fields are missing or incorrectly formatted.