The automation editor lets you build scenarios without writing any code. You can define a trigger, then organize your actions around conditions and conditional branches.
First, select what starts your automation:
Field change (e.g., when the Status field changes).
Form submission.
Permalink click.
Incoming webhook.
Recurring schedule (e.g., every Monday morning).
Once the trigger is selected, insert a condition block.
{} IF : first condition to evaluate.
{} Else if : additional conditions, evaluated if the previous one is false.
{} Else : default path, executed when no condition matches.
In the example, the three branches (IF, Else if, Else) appear side by side, each leading to its own actions.
➕ Create multiple conditions (IF / Else if / Else)
Add a first IF block
In the visual editor, insert a {} IF block by clicking
The setup window opens → configure and save
Example: If the Status field = Urgent
Open the {} IF context menu
Right-click the {} IF
block.
A small pop-up appears with options:
delete the condition block
add action
conditional branching
Add another condition
Click conditional branching.
A new block appears next to it: {} Else if
Repeat to add as many conditions as needed.
Each condition can have its own actions.
Add a default branch {} Else
When you’re done adding conditions, finish with an {} Else branch.
It runs if none of the previous conditions match.
You can chain as many logical conditions as you need — there is no technical limit.
Delete a branch
Right-click the {} Else if or {} Else block.
A small pop-up appears with options:
delete the condition block
add action
Preview a block’s configured condition
Hover a block to display the detailed tooltip configured for that condition.
👉 Result: your scenario reads left to right:
IF (when the first condition is true) → corresponding actions.
Else if (when another condition is true) → other actions.
Else (when no condition matches) → default scenario.
In this example, the automation starts when the Status field is modified.
A first If block checks a condition.
If true, two actions run in sequence:
Then write into one or more fields.
Then write into one or more fields (additional action).
Then a new conditional branch unfolds:
If the condition is true → Then add a new record.
Else → Then write into one or more fields.
👉 This illustrates a logic tree with multiple conditional branches.
In TimeTonic’s automation editor, each condition adapts to the selected column type.
The logic always relies on the pair 1️⃣ field + 2️⃣ operator.
- Text column → operators such as contains, begins with, is empty…
-
Number column → operators such as
=,<,>,≥… - Date column → comparisons with today, before, after, in x days…
- Select column → values are suggested automatically (is, is not, is any of, is not any of…).
Open the lists ▶️ below to see the operators available for each column type in the condition dialog:
1️⃣ Text — available operators
📌 Use these to check the contents of a text field.
-
Contains / Does not contain → (a word, phrase, or exact value)
-
Is / Is not → (strict equality with an exact value)
-
Contains the user’s TimeTonic @ID / Does not contain the user’s TimeTonic @ID → (handy to target a person or role)
-
Contains the workspace ID → (useful to filter for a specific workspace)
-
Begins with → (a given character sequence)
-
Is empty / Is not empty → (whether the field is filled)
2️⃣ Select — available operators
📌 Conditions are based on predefined choices from the dropdown.
-
Is / Is not → (strict comparison with a list value)
-
Is any of / Is not any of → (matches one or several choices from the list)
-
Contains / Does not contain → (searches a word or partial text within the selected choice)
-
Contains the user’s TimeTonic @ID / Does not contain the user’s TimeTonic @ID → (filter by a user linked to the selection)
-
Is empty / Is not empty → (when no choice is selected)
3️⃣ Date — available operators
📌 Compare dates against time references.
-
Is / Is not → (comparison with an exact date)
-
Before / After → (check whether a date is earlier or later than another)
-
On / Not on → (exact date, e.g., “on March 15, 2024”)
-
Today / Not today → (special case of equality with today)
-
Tomorrow → (exactly the next day)
-
Before today / After today → (strict comparison against today)
-
In this week / In this month / In this year → (dynamic ranges)
-
Not in the current month / Not in the current year → (exclude the current period)
-
In the next x days / In the previous x days → (relative window around a date)
-
In quarter → (useful for finance / HR reporting)
-
Is empty / Is not empty → (whether the field is filled)
4️⃣ Number — available operators
📌 Compare numeric values.
-
= / ≠ → equality or difference with an exact value
-
< / > → strictly less than / strictly greater than
-
≤ / ≥ → less than or equal / greater than or equal
-
Is group minimum / Is group maximum → smallest / largest value within a group (grouped view, group filter)
-
Is group lowest / Is group highest → extremes computed on the current set (useful to spot outliers/records)
-
Is empty / Is not empty → whether the numeric field is filled
⚡ Key reminders:
You can add as many conditions and branches as needed (no technical limit).
Each block can run several actions in sequence.
Scenarios are read top to bottom and left to right across branches.
To keep things readable, document your scenarios and avoid overly deep trees.