Skip to main content

HTTP Trigger

What it does​

Starts a workflow when an HTTP request hits the published gateway route. It exposes request method, path, headers, query, and body to downstream nodes.

Inputs/config​

  • Route and method are defined by the proxy/workflow wiring.
  • Optional header/query/path constraints can be enforced upstream.
  • No branch-specific config on this node.

Outputs/branches​

  • No matched_output.
  • Follows standard outgoing edge to the next node.
  • Emits request context for downstream expressions.

Example usage snippet​

{
  "id": "n1",
  "type": "http_trigger"
}

Common pitfalls​

  • Assuming this node validates payloads automatically; use validate_node.
  • Forgetting to terminate request flows with response_node or redirect_node.
  • Reading missing fields without null checks in downstream expressions.