Core Concepts
Understanding how Mindlyr structures your business rules and automations.
Workflow & Hierarchy
Mindlyr is organized into a four-level hierarchy designed for agency work and complex organizations.
Organization
The top-level entity, usually your Agency. Manages billing, global members, and security.
Business
Equivalent to a Client or a specific Department. Each business has its own team and projects.
Project
A container for related logic. For example, "Marketing CRM Automations" for a specific client.
Rule
The individual decision logic. This is what you execute via API (e.g., "Lead Qualification").
Versioning System
Mindlyr uses a robust versioning system to ensure you can update logic without breaking production workflows.
Development
Where you build and test new logic. Changes are instant and private.
Pilot Testing
Shared environment for testing with real-world staging data.
Live traffic
Immutably locked version serving production traffic via API.
Rule of thumb: Always keep your Staging rules synced with your Production logic, then promote a Draft to Staging for final verification before pushing to Production.
Rule Engine (JsonLogic)
Mindlyr uses the industry-standard JsonLogic format to represent rules. This allows for complex nesting and high-performance evaluation.
{
"and": [
{ ">": [{ "var": "lead_score" }, 80] },
{ "in": [{ "var": "country" }, ["US", "UK", "CA"]] }
]
}Schema Validation
Every rule corresponds to a JSON Schema. Mindlyr validates incoming data before processing, providing clear error messages if the data structure is invalid.
Input Schema
Guarantees that mandatory fields like customer_id or price are present and of the correct type.
Output Schema
Ensures your automations (n8n/Make) always receive a predictable payload.