Requisicao Externa uChat Trigger

Recebe requisições externas do uChat via webhook
Join our community

Overview

This node acts as a webhook trigger for receiving external requests from uChat. It listens for HTTP requests on a specified path and method, then triggers the workflow with the received data. It supports various HTTP methods and flexible response modes, including immediate response, response after the last node finishes, or using a dedicated response node. This node is useful for integrating uChat with other systems, automating workflows based on incoming messages or events from uChat.

Use Case Examples

  1. Trigger a workflow when a new message is received in uChat by setting the webhook path and HTTP method to POST.
  2. Use the node to listen for GET requests from uChat and respond immediately with a custom status code and headers.
  3. Configure the node to respond only after the entire workflow finishes processing, returning the first entry's JSON data.

Properties

Name Meaning
HTTP Method The HTTP method to listen for incoming requests (e.g., GET, POST, PUT).
Path The URL path on which the webhook listens for incoming requests.
Authentication The authentication method to use for incoming requests (currently only 'None' is supported).
Respond When to send the HTTP response back to the requester.
Response Code The HTTP status code to return in the response (only applicable if responding immediately or after last node).
Response Data The data to return in the response body when responding after the last node finishes.
Options.Binary Property The name of the binary property to return when responding with binary data.
Options.Response Headers Custom HTTP headers to add to the response.

Output

JSON

  • body - The body of the incoming HTTP request.
  • headers - The headers of the incoming HTTP request.
  • query - The query parameters of the incoming HTTP request.

Troubleshooting

  • If the webhook does not trigger, ensure the HTTP method and path match the incoming request.
  • If the response is not as expected, check the response mode and response code settings.
  • Custom response headers must be correctly formatted; otherwise, they may be ignored or cause errors.

Links

Discussion