SSW WhatsApp Trigger icon

SSW WhatsApp Trigger

Listens for webhooks from SSW API

SSW WhatsApp Trigger

AI-generated

Overview

This node listens for incoming webhook events from the SSW WhatsApp API. It is designed to trigger workflows in n8n when specific WhatsApp events occur on a selected device. Common use cases include automating responses to received messages, logging message data, or integrating WhatsApp communication into broader business processes.

For example, you could use this node to:

  • Automatically process and respond to customer messages received on a particular WhatsApp device.
  • Trigger notifications or CRM updates when new messages arrive.
  • Collect and analyze message data for reporting purposes.

Properties

Name Meaning
Webhook Name Unique identifier for the webhook endpoint. This name must be unique across your n8n instance.
Device Name or ID Select a WhatsApp device from a dynamically loaded list or specify its ID via an expression.
Event Types Choose which event types to listen for. Currently supports: "Message Received".

Output

The node outputs JSON data representing the webhook payload received from the SSW WhatsApp API, enriched with additional fields:

  • event_name: The type of event received (e.g., "message_received").
  • device_name: The name of the device that generated the event.
  • data: Contains detailed information about the message event.
  • chatInput: The actual message content extracted from the event data.
  • sessionId: The conversation ID associated with the message.

If the event does not match the selected event types, or if it originates from a different device than specified, or if the message is sent by the user themselves, the node will ignore the webhook and produce no output.

No binary data output is produced by this node.

Dependencies

  • Requires an API key credential for authenticating with the SSW WhatsApp API.
  • The node dynamically loads available devices from the SSW API endpoint https://app.supersimplewhats.com/v1/devices/list.
  • Proper configuration of the webhook URL path using the unique webhook name is necessary for receiving events.

Troubleshooting

  • Webhook Not Triggering: Ensure the webhook name is unique and correctly configured in both n8n and the SSW WhatsApp API settings.
  • No Data Output: Check that the incoming event matches the selected device and event types. Events from other devices or unselected event types are ignored.
  • Failed to Load Devices: If device loading fails, verify the API key credential is valid and has proper permissions. Network issues or API downtime can also cause failures.
  • JSON Parsing Errors: The node attempts to parse the webhook body; malformed JSON payloads may cause errors logged as "Failed to parse webhook body".
  • Ignoring Self-Sent Messages: Messages sent by the user themselves are intentionally ignored to prevent workflow loops.

Links and References

Discussion