Skip to main content
Observability in Brain Studio lets you register tracking events directly from your node configuration, so you can understand how users interact at each point of your workflow. These events feed your metrics and performance dashboards.

​
How does it work?

Node configuration panels such as HTTP, SOAP, Code, Tool, Conditional, Skill, and AI Agent, among others, include an Events tab. From there you can register up to 10 events per node, each with its own name, emission condition, and custom properties. When a node has events configured, you’ll see a badge underneath it on the canvas summarizing the active events. If none are configured, the badge shows “No active events”.

​
Configure an event

1

Open the Events tab

Select the node you want to instrument and go to its configuration panel. Next to the General tab you’ll find the Events tab, titled “Event configuration”.
2

Add an event

Click “Add event” and fill in the “Event name” field. The name must be in snake_case (for example, payment_attempted or appointment_scheduled); if it doesn’t match that format, you’ll see the error “Must be snake_case”.
3

Add properties (optional)

Under “Event properties”, use “Add field” to include up to 5 key/value pairs. The value can be a dynamic variable, such as {{$context.amount}} or {{$memory.customer_name}}.
Check the available Context Variables to see what data you can include in your event’s payload.
Limits per node: up to 10 events, each with up to 5 properties. Event and property names must be written in snake_case.

​
Practical example

You have a Tool node called “Charge Payment” that processes a charge. You configure an event like this:
  • Event name: payment_attempted
  • When to register the event: Success
  • Event properties:
    • amount: {{$context.amount}}
    • method: {{$context.payment_method}}
Every time the node completes a charge successfully, this event is registered with the amount and payment method used, ready to be analyzed in your metrics.
You have an API node that queries an external system. You configure an event to catch failures:
  • Event name: external_query_failed
  • When to register the event: Error
  • Event properties:
    • error_code: {{$context.statusCode}}
This lets you quickly identify how often and why that integration fails.
This capability is being rolled out progressively to companies in Brain Studio.

Brain Studio Nodes

Learn about all available node types and how to configure them.

Context Variables

Learn to use $context and other variables available during execution.

Your First Workflow

Learn to build your first workflow from scratch.