sipgate AI Flow Trigger
AI-generatedSummary
Receive and authenticate webhook events from the sipgate AI Flow voice assistant, routing each event type to a specific output or fallback based on configuration.
Inputs
- Authentication (required) — Selects the authentication method for incoming webhook requests: header-based or none.
- Header Name (required) — Specifies the name of the HTTP header containing the authentication token when header authentication is used.
- Header Value (required) — The expected value of the authentication header to verify webhook requests when header authentication is enabled.
- Include Barge-In Flag (required) — Determines whether to include the 'barged_in' flag in user_speak event data, indicating that the user interrupted the assistant.
- Debug Mode (required) — Enables inclusion of debug information in the output, such as raw request body and event type.
- Fallback Behavior (required) — Configures how events are routed to the fallback output: either all events route to fallback, or only unknown event types.
Output shape
Multiple outputs corresponding to specific sipgate AI Flow event types or fallback.
The node provides nine outputs labeled: 'Session Start', 'User Speak', 'Assistant Speak', 'Assistant Speech Ended', 'User Input Timeout', 'Session End', 'Fallback', 'DTMF Received', and 'SMS Failed'. Incoming events are dispatched to the appropriate output based on their 'type' field. If fallback behavior is set to 'allEvents', all events go to the fallback output; otherwise, only unrecognized event types do. The output data includes event JSON with optional removal of the 'barged_in' flag based on settings. Authentication failure returns an HTTP 401 error response; missing event type returns 400 error response.