Automation in Biznsbook: An Overview
Business Automation runs no-code workflows when something happens in your ERP. A trigger fires, optional conditions filter the event, then actions run — email, notifications, webhooks, field updates, CRM tasks, delays, and more.
Automation reacts to events from other modules. It does not replace module-specific rules (for example Expense approval stages).
What you can do
- Build workflows with a step list or a visual canvas
- Trigger on events from CRM, Expense, Inventory, Sales, Purchase, HR, Scheduling, and other licensed modules
- Add conditions (all must match, or any must match)
- Run actions such as send email, notify, webhook, update field, create task, delay, and enroll in a drip sequence
- Start from a template, then customise
- Review execution logs, retry failed runs, and keep workflows active only when they behave
How a workflow runs
Event happens → Matching active workflows
→ Conditions (optional) → Actions / steps
→ Logged under Execution Logs
New workflows start inactive. Activate them from the dashboard when you are ready for live events.
Before you start
| You'll need | Why |
|---|---|
| Business Automation module licensed | Shows the Automation menu |
| Automation access on your role | Opens builders, templates, and logs |
| An active company context | Workflows are company-scoped |
| Communication Center (recommended) | Send email and drip-sequence actions |
| Source modules licensed | Triggers only fire for modules you use |
| Email Settings configured | Delivery for Send email steps |
Finding your way around
| Menu item | Purpose |
|---|---|
| Workflows | List, stats, activate / deactivate, duplicate |
| New Workflow | Step-based builder |
| Visual Builder | Drag-and-drop canvas |
| Templates | Prebuilt patterns you can copy |
| Execution Logs | Run history, errors, and retries |
Recommended order
- Before you start with Automation
- Create and activate a workflow
- Use workflow templates
- Monitor execution logs