Automation Table Page

- What the Automation Table Page Is
 

The Automation Table page is the central control room for all workflow automations in the system.
 

It is the place where users can see, manage, control, and organize every automation rule that exists in their account.
 

This page does not execute actions itself — instead, it defines when and under what conditions automated actions should run, and in what priority order.
 

In simple terms:

If the system has a “brain”, the Automation Table is where all the rules of that brain live.

 


- Why This Page Exists (Business Purpose)
 

Modern systems generate many events:
 

  • New leads

  • Status changes

  • Payments

  • Appointments

  • Documents

  • Orders

  • Messages

  • Subscriptions
     

Manually reacting to all of these is:
 

  • Slow

  • Error-prone

  • Expensive

  • Not scalable
     

The Automation Table page exists to:
 

  • Remove manual work

  • Ensure consistent responses

  • Automate repetitive actions

  • Connect different modules together

  • Let the system work even when users are offline
     


- What Problems It Solves
 

Without this page:
 

  • Teams forget to follow up

  • Emails are sent late

  • Status changes don’t trigger actions

  • Data becomes inconsistent

  • Work depends on humans remembering steps
     

With this page:
 

  • Actions happen automatically

  • Rules are documented and visible

  • Behavior is predictable

  • Scaling is easy

  • Errors are reduced
     


- What This Page Controls (At a High Level)
 

The Automation Table defines automation rules, each rule consisting of:
 

  1. WHEN something happens (Event)

  2. IF certain conditions are met (Parameters & Filters)

  3. WAIT for some time (Optional Delay)

  4. THEN DO one or more actions (Configured elsewhere)
     

This page focuses on steps 1–3 and the management of rules.
 


- Visual Structure & Layout (How the Page Looks)
 

The page is built as a clean, structured table with:
 

  • Clear rows (one row = one automation)

  • Icons instead of long text

  • Toggles instead of buttons

  • Actions grouped visually

  • Priority ordering by drag & drop
     

It is designed for quick scanning, not reading long descriptions.
 


- The Automation Table (Core Area)
 

Each row in the table represents one automation rule.
 

What One Row Means
 

A single row answers these questions instantly:
 

  • What is this automation called?

  • What event triggers it?

  • Is it active or inactive?

  • What can I do with it?
     


- Automation Number (NO.)
 

  • A unique identifier for internal reference
     

  • Useful for:
     

    • Logs

    • Debugging

    • Support discussions
       

  • Also helps track execution priority
     


- Automation Name
 

  • Human-readable description of the rule

  • Written by the user

  • Should clearly describe purpose, for example:

    • “Send welcome email on new lead”

    • “Create mission after invoice paid”
       

This name is critical for maintainability.
 


⚡ Event (Trigger)
 

This column defines WHEN the automation starts.
 

Examples:
 

  • New lead created

  • Status changed

  • Payment received

  • Appointment booked

  • Document signed
     

The event is the entry point of the automation lifecycle.
 


- Parameter (Conditions)
 

Parameters define which exact situations qualify.
 

They answer:
 

  • Which folder?

  • Which tag?

  • Which status?

  • Which amount?

  • Which custom field value?
     

This allows:
 

  • Precision

  • Filtering

  • Avoiding unnecessary automation runs
     


✅ Active / ❌ Deactive Toggle
 

This is a live switch.
 

  • Active → automation is evaluated and executed

  • Deactive → automation is ignored completely
     

Why this matters:
 

  • Safe testing

  • Temporary disabling

  • Seasonal workflows

  • Emergency stop without deletion

     

    ➕ Creating a New Automation (User Journey)
     

  • User clicks “+ NEW AUTOMATION”

  • A modal opens
     

  • User defines:
     

    • Automation name

    • Event

    • Parameters

    • Include/exclude rules

    • Delay (optional)
       

  • User saves

  • Automation appears in the table

  • User configures actions via the flow builder

  • This separation keeps:

  • Rules clean

  • Actions flexible

  • System modular
     

  • - How Automations Actually Work (Behind the Scenes)
     

    Event-Driven Execution Model
     

  • A system event occurs

  • The automation engine is called

  • It loads all active automations for that event
     

  • It evaluates:
     

    • Parameters

    • Include/exclude values

    • Custom field logic

    • Secondary conditions
       

  • Matching automations are processed in order

  • Actions are executed immediately or scheduled
     

  • ⏱️ Delay System (Time-Based Intelligence)
     

    Automations don’t always run instantly.
     

    Delays allow:
     

  • Follow-ups after X hours

  • Reminders after X days

  • Scheduled workflows
     

  • Delays can be defined in:
     

  • Minutes

  • Hours

  • Days

  • Months
     

  • Internally, all delays are normalized into minutes, ensuring consistent execution.
     


    - Automation Execution Queue (Cron System)
     

    For delayed automations:
     

  • Jobs are stored in a queue

  • A background cron process runs regularly

  • Due jobs are executed

  • Old jobs are safely ignored

  • Executed jobs are removed
     

  • This ensures:
     

  • Reliability

  • Scalability

  • Non-blocking performance
     

  • - Copying Automations (Best Practice Feature)
     

    Copying automations allows:
     

  • Faster setup

  • Reuse of logic

  • Small variations without re-creation

  • Copied automations:

  • Get a new ID

  • Copy all conditions

  • Copy all actions

  • Start as active

     

    - Automation Logs & Monitoring
     

    From the table, users can:
     

  • Open execution logs

  • See when automations ran

  • This builds trust in automation behavior.
     

  • - Security & Permissions
     

    The page respects:
     

  • Organization isolation

  • Role-based permissions

  • Edit/create/delete rights

  • Only authorized users can:

  • Create automations

  • Edit rules

  • Activate/deactivate

  • Delete workflows
     

  • - Performance & Scalability
     

    The Automation Table is optimized for:
     

  • Large numbers of automations

  • Fast filtering

  • Minimal DB queries

  • Cached definitions

  • Batch execution

  • Even large organizations can run hundreds of automations safely.
     

    - How Users Typically Use This Page
     

  • Admins design workflows

  • Managers review active rules

  • Teams disable rules temporarily

  • Support audits automation behavior

  • Developers debug event logic

  • It becomes a living map of business logic.
     

    - How This Page Connects to the Whole System
     

    This page touches almost every module:
     

  • Customers

  • Status Controller

  • Orders

  • Documents

  • Appointments

  • Payments

  • Projects

  • Tickets

  • WhatsApp

  • SMS

  • Email

  • It is the glue that connects them.
     

    - Final Big-Picture Summary
     

    The Automation Table page is the rulebook of the system — defining how the platform reacts automatically to events, conditions, and time, without human intervention.


    ⭐ One-Line Description
     

    Automation Table lets you design, control, and monitor event-based workflows that run your business automatically.

     

     

information_img

מוצרים

מודולים

מאפיינים

מחירון

עלינו

צרו קשר

עוד

BIZ1 CRM
באינטרנט
איש קשר Biz1.co.il