AITEZA Trigger
AI-generatedSummary
Receives Aiteza events through an HTTP POST webhook and starts the workflow with the request body, headers, and query data. It can return immediately or wait for the last workflow node, and forwards available authentication tokens and an optional AITEZA base URL for downstream nodes.
Inputs
- Path (required) — Webhook path, default
aiteza; the full path is/webhook/{path}. - Response Mode — Choose
Immediately(default) to return 200 OK as soon as the webhook arrives, orWhen Last Node Finishesto respond with data from the last node. - AITEZA Base URL — Optional base URL forwarded to downstream Aiteza nodes as
_baseUrl; trailing slashes are removed. - Webhook request — Accepts an HTTP POST request. Request body, headers, and query parameters are included in the output. If the body contains
user.bearerToken, it is forwarded as_authToken; otherwise the Bearer token from the Authorization header is used. If optionalaitezaWebhookApicredentials are configured, the Authorization Bearer token must match the configured API key or the request receives 401 Unauthorized. A distinct header token is also forwarded as_serviceAuthToken.
Output shape
A single item containing body, headers, and query, with optional _authToken, _serviceAuthToken, and _baseUrl fields.
With
When Last Node Finishes, the webhook responds with all entries from the last node. WithImmediately, use the Aiteza Workflow Result node to send results back asynchronously. Unauthorized requests return 401 and do not produce workflow data.