Overview
This document defines the event model.All events in this document are append-only, immutable, and ordered by timestamp.
π Webhook vs Internal Events (IMPORTANT)
Not all events are sent to Antler. We separate events into two categories:1οΈβ£ Webhook Events (Sent to Antler)
Only the following events are pushed to the Antler webhook.
These events are business-critical and power Antlerβs downstream workflows.
2οΈβ£ Internal Events (Tracking & Monitoring Only)
All other events are NOT sent to Antler. They are used internally for:- Funnel tracking
- Debugging
- Reliability monitoring
- Conversation analytics
create_attempt, link_opened, candidate_ready, tracy_joined, face_detected, speech_detected, etc.
Webhook Payloads
Only the following events will be sent to Antler Webhook.Event: submit_form
Triggered when the founder submits the pitch deck.
The
co_founders field is a dynamic object where each key (co_founder_1, co_founder_2, β¦) represents a co-founder. Each co-founder object contains: co_founder_first_name, co_founder_last_name, co_founder_role, co_founder_email, co_founder_linkedin, and co_founder_phone. This field is null if no co-founders are provided.Event: report_generated
Triggered when the interview is completed and the report is ready.
- Run evaluation pipelines
- Store records
- Trigger investment or screening workflows
Field Definitions
Core Identifiers
-
conversation_idUnique identifier for the conversation (unique for each attempt). Create a newconversation_idif the founder retries again. -
founder_emailFounder email address used for identification and notifications.
Event Metadata
-
event_nameCanonical event name emitted by Qode (example:submit_form,report_generated). -
timestampUTC timestamp indicating when the event occurred.
Co-founders
Theco_founders field is a dynamic object supporting multiple co-founders. Each co-founder is keyed as co_founder_1, co_founder_2, etc.
Each co-founder object contains: