bitaliRules grounded in objects
Define conditions over object sets and choose how the automation is triggered.
AutomateAction & intelligence
When conditions change, work moves.
Describe the condition that deserves attention and the response that should follow. Automate evaluates the rule and runs its configured effects, with execution history available for review.
Inventory watchILLUSTRATIVE RULE
TRIGGEROn a scheduleReview stock objects
CONDITIONBelow the reorder point?Available stock < threshold
Condition met
EFFECTNotify the team
Otherwise
No effect
Rule → evaluation → execution history
MAKE THE RESPONSE EXPLICIT
When this happens, do that.
A rule is a connection between a situation and a response. Define both, then keep a record of what runs.
WHENObjects meet a condition
Object setConditionSchedule
THENRun the configured effects
NotificationObject actionWebhook
A configured response
Use supported effects such as notifications, object actions, and webhooks.
THE LIFE OF A RULE
A response you can follow.
Describe the condition
Choose the relevant object set and the condition or schedule to evaluate.
Choose the response
Configure the effects, their inputs, and the recipients where needed.
Activate and review
Enable the automation and use its execution history to follow the results.
Execution historyILLUSTRATIVE
SAMPLE RUN ACondition matched
Configured notification completed.
SAMPLE RUN BNo matching objects
The rule ran without an effect.
SAMPLE RUN CNeeds attention
Review the failed effect and its inputs.
Explore every part
FROM DATA TO ACTION
See the bigger picture.
Explore how the tools work together, from data to action.