Skip to main content
A workflow execution is the main metric unit in Brain Studio. It represents the complete cycle from when a flow is triggered until it finishes its work, regardless of how many messages are exchanged or how many internal steps are executed.

​
Key concepts

​
Skills vs Tools

Skill

Designed to converse with users. Contains message nodes (text, images, buttons) and logic nodes (code, API, conditionals).

Tool

Designed to execute technical operations. Only contains logic nodes. It does not converse, it only processes.

​
What counts as an execution?

The rule is simple: one flow start = one execution, regardless of how many internal processes are executed.
1

Scenario 1: Main Skill

You start a Skill called “Customer Support”. During the conversation:
  • The Skill exchanges 20 messages with the user
  • Calls a “Check Balance” Tool
  • Transfers to another Skill “Satisfaction Survey”
Result: one execution
2

Scenario 2: Independent Tool

You directly execute a Tool via API (without going through a Skill):
  • The Tool performs its calculation and finishes
Result: one execution
Tools cannot call other Skills or Tools. They are atomic units.

​
What is included in the cost?

​
✅ Included in one execution

  • The start of the flow (Skill or Tool)
  • All internal transfers (Skill → Skill)
  • The use of internal tools (Skill → Tool)
  • Unlimited messages within the same session

​
💰 Billed separately

  • AI model tokens: Natural language processing is billed according to model usage (GPT-4, Claude, etc.)
  • KYC: Identity verifications have an independent cost per validation performed.
  • Electronic signature: Each signature process is billed individually.
  • Transactional Tools: Tools that perform transactional operations (payments, charges, etc.) have their own rate per transaction executed.

​
Practical examples

A user starts a conversation → your “Support” Skill attends them → calls 3 different Tools (validate user, query history, create ticket) → transfers to “Escalation” Skill → closes the conversation.Total: 1 execution
A user contacts you 3 times in the same day:
  • 9:00 AM - Asks about their balance
  • 2:00 PM - Requests a report
  • 6:00 PM - Asks to update their data
Total: 3 executions (each conversation starts a new flow)
Your external system calls the “Calculate Discount” Tool 50 times during the day.Total: 50 executions

​
Getting an execution ID

When you start an execution, you receive a unique identifier (executionId) that Brain Studio generates automatically. This ID remains constant throughout the entire execution, even if you transfer the flow between Skills or call Tools. You can access it from any node using: 
  {{$context.executionId}}

​
Summary

In Brain Studio, you pay for solving complete problems, not for each step of the process. This lets you create complex flows and long conversations without worrying about increasing costs.
The execution architecture encourages modularity: you can orchestrate complex flows (Skill → Tool → Skill) without inflating costs, allowing you to focus on creating the best possible experience.

How billing works

Key concepts about organization-level billing in Jelou.

Pricing

Pricing details for conversations, campaigns, and Connect seats.

Your First Tool

Create your first Tool from scratch and publish it to reuse it in your flows.

Skills with AI

Configure an AI Agent that collects data from your users.

Context Variables

Access the executionId and other variables available during execution.