​
The Logic of Automation

Every automation rule in Luklak, no matter how complex, is built on a simple, three-part foundation: the Trigger, the Condition, and the Action. Mastering this T-C-A model is the key to building any automated process. In simple terms, every rule answers three questions:
  1. When should this automation run? (The Trigger)
  2. If the conditions are right… (The Condition)
  3. Then do the following work. (The Action)

​
Deconstructing the T-C-A Model

Let’s break down each component.

The Trigger is the specific event that starts your automation rule. The automation engine is constantly listening for this event to occur.

Examples: “When a new 🧊 Deal Object is created,” “When the Status of a 🧊 Task is updated to DONE,” or “Every Monday at 9:00 AM.”

Think of it as: The starting pistol for a race.

For a complete list of all possible starting events, see our Guide to Trigger Types.

​
Controlling the Flow: Execution Logic

Beyond a simple linear path, you can build sophisticated logic within your rule’s ‘Condition’ block to handle different scenarios. This is known as the Execution Flow.

If/Else Flow

The most basic logic. IF the condition is true, perform Action A. ELSE, perform Action B. Perfect for simple binary decisions.

Multi-Path Flow

Create multiple parallel paths based on different conditions. For example: If Priority is HIGH, notify manager. If Type is BUG, create Jira ticket.

Branching Flow

Used when your rule finds multiple 🧊 Objects. A Branching flow iterates through each found 🧊 Object and applies the actions to each one individually.
[Guidejar Placeholder: A tutorial that builds a simple rule from scratch. Trigger: ‘When a Deal is created’. Condition: ‘If Deal Value > $5000’. Action: ‘Send a message to the #deals channel’. This will make the T-C-A model concrete.]

​
What’s Next?

You’ve mastered the basic logic and structure of an automation rule. Now, let’s explore the full range of possibilities for each component.