Requisicao Externa NicoChat Trigger icon

Requisicao Externa NicoChat Trigger

Recebe requisições externas do NicoChat via webhook

Requisicao Externa NicoChat Trigger

AI-generated

Summary

Receive and trigger workflows on external HTTP requests sent to a configurable webhook path with the specified HTTP method, optionally setting response code and headers, and control when to send the HTTP response.

Inputs

  • HTTP Method — The HTTP method (GET, POST, PUT, PATCH, DELETE, HEAD) to listen for incoming requests.
  • Path (required) — The URL path on which to listen for incoming webhook requests.
  • Authentication — Authentication method to apply; currently only 'None' is supported.
  • Respond — When to send the HTTP response: immediately on webhook receipt, after workflow finishes, or using a dedicated respond node.
  • Response Code — The HTTP status code to return when responding (used unless responding via dedicated respond node).
  • Response Data — Data to return in the HTTP response body when responding after the last node finishes; options include all input items, first item's JSON, first item's binary data, or no data.
  • Binary Property — The binary property name to return when choosing to respond with binary data.
  • Response Headers — Custom HTTP headers to include in the response.

Output shape

a single array containing one JSON object with keys 'body', 'headers', and 'query' representing the incoming request's body, headers, and query parameters.

No authentication is enforced. The output always contains the request data structured as JSON. Response behavior depends on 'Respond' parameter: immediate response uses provided status and headers; deferred response options vary in content returned. Custom response headers can be set.

Discussion