Skip to main content
Version: 2.11

Olympe Bricks API

The Bricks API is a rich library of pre-created Bricks that allow you to create complex logic without writing everything from scratch. These Bricks are organized into two main collections:

Core​

The Core collection includes the most fundamental and frequently used Bricks. These are essential for building general-purpose logic and handling basic operations.

You’ll find Bricks like:

  • If: Conditional branching
  • And, Or: Logical gates
  • Switch: Multi-branch logic
  • For Each: Iteration over collections
  • Map: Data transformation

These Bricks are readily available in any composition and serve as the building blocks of most applications.

Extensions​

The Extensions collection provides a wide array of Bricks designed for more specific or situational needs. These Bricks are organized into packages that can be imported individually based on your use case.

Some examples include:

  • OAuth Bricks for authentication flows
  • Email Bricks for sending and receiving messages
  • File formatting Bricks for formatting files Extensions enable you to plug in functionality as needed, keeping your base composition lean while giving you flexibility.

Brick types​

Logic Bricks come in two types, each serving a different purpose in your logic:

Function

A Function Brick behaves like a computed value or transformation logic. It:

  • Has inputs (parameters) and outputs (return values)
  • Starts executing only once all its inputs are resolved
  • Automatically re-evaluates whenever one of its inputs changes
  • Continues this behavior until the context is destroyed (e.g., the user navigates away)

This makes Functions ideal for live data transformations and dynamic logic that reacts to changes over time.

Action

An Action Brick represents a triggered behavior. It:

  • Executes immediately when the Control Flow that triggers it is activated
  • Does not wait for other inputs to resolve (though they can still be read if available)

Actions are typically used for responding to events, such as:

  • Button clicks
  • Screen navigation
  • Backend responses

Use Actions when you want something to happen right away based on a specific event.