Wapisimo TriggerInstall

Overview

The Wapisimo Trigger node is designed to handle webhook events from the Wapisimo service within n8n workflows. It listens for specific events (such as "Message Received") sent by Wapisimo to a configured webhook URL, and triggers the workflow when such events occur. This node is particularly useful for automating processes in response to incoming messages or other real-time events from Wapisimo.

Common scenarios:

• Automatically processing or responding to WhatsApp messages received via Wapisimo.
• Integrating Wapisimo message events with other services (e.g., CRM, notifications).
• Logging or analyzing incoming communication for business intelligence.

Practical example:
A business could use this node to trigger an n8n workflow whenever a new WhatsApp message is received, automatically creating a support ticket or sending an acknowledgment reply.

Properties

Output

The node outputs the JSON payload received from the Wapisimo webhook. The structure of the output depends on the data sent by Wapisimo for the selected event(s). Typically, it will include all fields provided in the webhook POST body.

Example output:

[
  {
    // All fields as received from Wapisimo webhook, e.g.:
    "event": "messageReceived",
    "data": {
      "from": "+1234567890",
      "message": "Hello!",
      // ...other fields
    }
  }
]

• If the webhook is not found, the output will contain an error field:

[
  {
    "error": "Webhook not found"
  }
]

Dependencies

• External Service: Requires access to the Wapisimo API.
• API Key: You must provide valid Wapisimo API credentials (wapiSimoApi).
• n8n Configuration: The node must be accessible from the internet so Wapisimo can reach its webhook endpoint.

Troubleshooting

Common issues:

• Invalid Credentials: If the API key or base URL is incorrect, the node will throw authentication errors.
• Webhook Not Registered: If the webhook cannot be registered or deleted, check your Wapisimo account permissions and ensure the phoneId parameter is correct.
• Network Issues: Ensure that your n8n instance is publicly accessible for Wapisimo to deliver webhook events.

Error messages:

• "Webhook not found": The webhook endpoint was accessed with an invalid path or before registration. Make sure the webhook is properly set up in Wapisimo.
• Errors thrown by the node (wrapped in NodeApiError) will include details from the Wapisimo API response. Check the error message and description for troubleshooting.

Links and References

• Wapisimo Documentation
• n8n Webhook Documentation
• n8n Credentials Setup