Skip to content

Event Driven App

An event driven application reacts to events obtained from the Unique platform. These events can be used to initialize services that in turn have effect on the chat, knowledge base or the agentic table.

For a secure application it is paramount that successive events do not have any effect onto each other, thus ideally your functionality is stateless and all necessary state is obtained via the services of the Unique Platform.

Events

The unique platform sends out events to dedictate endpoints (Webhooks) or registered clients (SSE).

Development Setup

Register App in Platform

Whether we use the SSE client to initiate the connection from the Python code or we expose the webhook via a URL, the app needs to be registered as explained here

Option 1: Connecting via SSE Client

Using an SSE client we can connect to the event stream of the unique platform. Find more here.

Option 2: Exposing an Endpoint to the Unique Platform

Setting up a FastAPI application and exposing the local endpoint via ngrok and the web, we can register this endpoint directly within the Unique platform. More here

Filtering Chat Events

Applications using events are responsible to decide how to react to them and to configure what events should be dropped. Chat events may be filtered by the following two environment variables

1
2
UNIQUE_CHAT_EVENT_FILTER_OPTIONS_ASSISTANT_IDS=
UNIQUE_CHAT_EVENT_FILTER_OPTIONS_REFERENCES_IN_CODE=

these variables will be automatically caught by the settings and filter the events that reach the handlers.

An example would look as follows

1
2
UNIQUE_CHAT_EVENT_FILTER_OPTIONS_ASSISTANT_IDS=["assistant_i34ys925m8zi5n6ptobbnwl1"]
UNIQUE_CHAT_EVENT_FILTER_OPTIONS_REFERENCES_IN_CODE=["AcademyTestModule"]

⚠️ Events are filtered by default if none of the above variables are defined when using our SSE or FastAPI setup.

How Filtering Works

Filtering happens automatically before your event handler is called. Events that don't match the filter criteria are silently dropped. This helps ensure your application only processes relevant events.

  • If UNIQUE_CHAT_EVENT_FILTER_OPTIONS_ASSISTANT_IDS is set, only events for those assistant IDs will be processed
  • If UNIQUE_CHAT_EVENT_FILTER_OPTIONS_REFERENCES_IN_CODE is set, only events from modules with those references will be processed
  • If both are set, events must match both criteria
  • If neither is set, all events are filtered out (default behavior)

Service Initialization from Events

Once you have an event, you can initialize services directly from it:

#init_services_from_event
1
2
3
# Initialize services from event
chat_service = ChatService(event)
kb_service= KnowledgeBaseService.from_event(event)

️