Actions26
- Webhook Actions
- Session Actions
- User Actions
- Chat Actions
- Message Actions
Overview
The node "SteveChat" integrates with the SteveChat API to enable WhatsApp messaging functionalities. Specifically, for the Webhook resource and the Set Webhook operation, it allows users to configure a webhook URL that will receive event notifications from the SteveChat service. This is useful for scenarios where you want to automate workflows based on incoming WhatsApp messages or other related events by having them pushed to your specified endpoint.
Practical examples include:
- Setting up a webhook to receive new message notifications and trigger follow-up actions in n8n.
- Subscribing to read receipts or presence updates to monitor message status or user availability.
- Receiving history sync events to keep your system updated with past conversations.
Properties
| Name | Meaning |
|---|---|
| Webhook URL | The URL endpoint where the SteveChat service will send event notifications (e.g., https://example.com/webhook). This must be a publicly accessible URL capable of receiving HTTP requests. |
| Events | The types of events to subscribe to for this webhook. Options include: - All (subscribe to all event types) - Message (receive message events) - ReadReceipt (receive read receipt events) - Presence (receive presence events) - HistorySync (receive history sync events) - ChatPresence (receive chat presence events) |
Output
The node outputs JSON data representing the response from the SteveChat API after setting or updating the webhook subscription. This typically includes confirmation details about the webhook registration and subscribed events.
No binary data output is indicated for this operation.
Dependencies
- Requires an active connection to the SteveChat API via an API key credential configured in n8n.
- The webhook URL provided must be reachable from the internet to receive callbacks.
- Proper network and firewall settings should allow inbound HTTP requests to the webhook URL.
Troubleshooting
Common issues:
- Invalid or unreachable webhook URL: Ensure the URL is correct, publicly accessible, and can accept POST requests.
- Missing or incorrect API credentials: Verify that the API key credential is properly set up in n8n.
- Subscription errors due to unsupported event types: Confirm that selected events are valid as per the node's options.
Error messages:
"The resource \"webhook\" is not supported!"— Occurs if the resource parameter is incorrect; verify the resource name."The operation \"set\" is not supported for resource \"webhook\"!"— Happens if the operation parameter is invalid; check operation spelling and availability.- Network or authentication errors returned from the SteveChat API will appear in the node output; review API credentials and network connectivity.
Links and References
- SteveChat API Documentation (Replace with actual URL)
- n8n Webhook Concepts
- WhatsApp Business API Webhooks (For conceptual understanding)