StevoChat icon

StevoChat

Interact with StevoChat API

Actions12

Webhook → Set

AI-generated

Overview

The node integrates with the StevoChat API to manage webhooks for receiving event notifications. Specifically, the "Webhook" resource with the "Set" operation allows users to configure a webhook URL and subscribe to specific event types such as messages, contacts, groups, or chats. This is useful for automating workflows that react to real-time events from StevoChat, like new incoming messages or contact updates.

Practical examples include:

  • Setting up a webhook URL to receive notifications whenever a new message arrives, enabling automated processing or alerting.
  • Subscribing to group or chat events to track changes or activity within those entities.

Properties

Name Meaning
Webhook URL The URL endpoint where StevoChat will send event notifications.
Events The types of events to subscribe to. Options: Messages, Contacts, Groups, Chats.

Output

The node outputs a JSON array containing the response from the StevoChat API after setting the webhook. This typically includes confirmation details about the webhook subscription status.

No binary data output is involved in this operation.

Dependencies

  • Requires an active StevoChat API key credential configured in n8n.
  • Network access to the specified webhook URL must be available for StevoChat to deliver events.
  • The node uses HTTP POST requests to the /webhook endpoint of the StevoChat API.

Troubleshooting

  • Common issues:

    • Invalid or unreachable webhook URL: Ensure the URL is publicly accessible and correctly formatted.
    • Missing or incorrect API credentials: Verify that the API key is valid and properly set up in n8n.
    • Subscription to unsupported event types: Confirm that only supported event types (messages, contacts, groups, chats) are selected.

  • Error messages:

    • Errors returned by the API will be shown in the node output if "Continue On Fail" is enabled.
    • Typical errors may include authentication failures, invalid parameters, or network timeouts.

To resolve errors, check the webhook URL accessibility, validate input parameters, and ensure correct API credentials.

Links and References

Discussion