How to Build Event-Driven Workflows

Quick answer Open Automation → Visual Builder, drag a trigger such as Lead created or Stock low from the Triggers tab, add conditions and an IF/ELSE step from the Steps tab, and connect actions like send email, create task or send webhook. Click Test to see which path sample data takes, then save. An Automation Manager activates the workflow; from then on every matching event starts a run you can trace with Show path on canvas.

Manual follow-ups miss moments when events already fired

Sales and operations teams react to leads and stockouts hours later because nothing watches for a new lead or a low-stock event in real time.

CRM-only rules, spreadsheet reminders and one-off scripts each cover a slice of the business, so nobody can see which automations exist or who switched them on.

Scripts built outside the ERP lack tenant isolation and run history, so failures disappear without anyone noticing.

Workflows without a cooldown or daily limit flood webhooks when Stock low fires on every sync for the same SKU, causing external systems to rate-limit your integration.

When several workflows match the same event, duplicate emails go out unless priorities and run-once settings are configured deliberately.

Why this happens

  • Business Automation is not licensed, or workflows are saved but never activated by an Automation Manager.
  • Triggers are picked for events the builder marks Not yet emitted, so the workflow never starts.
  • Conditions are too broad, causing noisy webhook or email actions.
  • Failed runs are not reviewed on the Runs page.

Biznsbook addresses this through 190+ event triggers, visual workflow builder, IF/ELSE branching, Show path on canvas when Business Automation is licensed — modules publish events and workflows run in the background.

Teams lose hours each week to follow-ups, reminders and approvals that live in inboxes and spreadsheets. Making Biznsbook Automation the one place where these rules run — with roles deciding who can switch them on and run history showing what happened — stops silent gaps and duplicate messages.

Step-by-step: Build Event-Driven Workflows

Built for operations leads wiring event-driven workflows across CRM, Sales, Inventory, HRMS, Real Estate and the other modules Biznsbook Automation listens to.

  1. License Business Automation. Confirm Business Automation is licensed and that you hold the Automation Manager or Automation Builder role. Triggers only appear for modules your company uses.
  2. Open the Visual Builder. Go to Automation → Visual Builder, or choose Start from template to begin from a pattern that only uses modules your company has.
  3. Pick a trigger event. On the Triggers tab, filter by module and drag a trigger such as Lead created, Deal won or Stock low onto the canvas.
  4. Add conditions and branches. From the Steps tab, add a condition with a field, operator and value. There are 21 operators, combined with AND / OR groups. Add an IF/ELSE step when the Yes and No cases need different actions.
  5. Configure actions. Connect actions such as send email, send notification, create task, update field or send webhook. Use merge fields to put record values into messages.
  6. Test with sample data. Click Test for a dry run. It follows IF branches and highlights the path the sample data would take, without sending anything.
  7. Activate and monitor. An Automation Manager saves and activates the workflow; a Builder uses Save & request activation instead. Review the Runs page and use Show path on canvas to see the steps each real run took.
  8. Set priority and run rules. Open Settings in the builder. When several workflows share a trigger, give customer-facing ones a higher priority, and add a cooldown, run once per record or a daily limit so the same record does not re-fire every few minutes.
  9. Review failed runs. Check the Runs page after webhook failures, fix the payload or URL, then retry the run from the failed step before switching high-volume workflows back on.

Review results after the first full weekly cycle. Adjust roles, mappings, or approvals where the same exception repeats.

Screen-level flows live in the Help Center. This guide focuses on the business process; help articles cover click-by-click navigation.

Common mistakes to avoid

  • Mistake 1: Business Automation is not licensed, or workflows are saved but never activated by an Automation Manager. Repeating this each month usually shows up first in failed runs or duplicate customer emails.
  • Mistake 2: Triggers are picked for events the builder marks Not yet emitted, so the workflow never starts. Repeating this each month usually shows up first in failed runs or duplicate customer emails.
  • Mistake 3: Conditions are too broad, causing noisy webhook or email actions. Repeating this each month usually shows up first in failed runs or duplicate customer emails.
  • Mistake 4: Failed runs are not reviewed on the Runs page. Repeating this each month usually shows up first in failed runs or duplicate customer emails.

Note each recurring failure on the Runs page in your weekly review; each should map to a step in this guide.

Best practices that hold up as you scale

  • License Business Automation — Confirm Business Automation is licensed and that you hold the Automation Manager or Automation Builder role.
  • Open the Visual Builder — Go to Automation → Visual Builder, or choose Start from template to begin from a pattern that only uses modules your company has.
  • Pick a trigger event — On the Triggers tab, filter by module and drag a trigger such as Lead created, Deal won or Stock low onto the canvas.
  • Add conditions and branches — From the Steps tab, add a condition with a field, operator and value.
  • Configure actions — Connect actions such as send email, send notification, create task, update field or send webhook.

Teams that start with one trigger like Lead created and add conditions before enabling webhooks avoid noisy automations.

How Biznsbook supports this workflow

190+ event triggers is part of Biznsbook Business Automation. Workflows are built on a visual canvas, tested with a dry run that follows IF branches, activated by an Automation Manager, and every run keeps each step's input and output.

visual workflow builder is part of Biznsbook Business Automation. Workflows are built on a visual canvas, tested with a dry run that follows IF branches, activated by an Automation Manager, and every run keeps each step's input and output.

IF/ELSE branching is part of Biznsbook Business Automation. Workflows are built on a visual canvas, tested with a dry run that follows IF branches, activated by an Automation Manager, and every run keeps each step's input and output.

Show path on canvas is part of Biznsbook Business Automation. Workflows are built on a visual canvas, tested with a dry run that follows IF branches, activated by an Automation Manager, and every run keeps each step's input and output.

Four Automation roles split the work: Managers activate and delete, Builders draft and request activation, Operators run, pause and retry, and Viewers read.

Suggested implementation timeline

  1. Week 1: List the follow-ups and approvals you repeat by hand and build a first draft with 190+ event triggers.
  2. Week 2: Test the draft with sample data, check the highlighted path, and have an Automation Manager activate it.
  3. Week 3: Review the Runs page daily, retry failed runs, and tighten conditions that fire too often.
  4. Week 4: Add branches, approvals or schedules where the first workflow proved its value.
  5. Ongoing: Weekly review using first workflow pattern and the Runs page.

Choosing triggers by department

Sales should start with Lead created and Deal won; operations with Stock low and Stock received; finance with Expense submitted and Expense approved. One department per first workflow reduces cross-team debugging.

Use AND / OR groups intentionally — AND narrows a run, OR broadens it, and groups such as A AND (B OR C) keep both readable. Test with sample data from a recent run so field paths match your data.

Branches, approvals and schedules

An IF/ELSE step splits a workflow into Yes and No paths, so a single workflow can email a customer when an order is small and ask a manager when it is large. A Find record step can look up a customer's balance or an item's stock before the next step, and an IF can use that result. The Test button shows which path sample data would take.

A Request approval step pauses the run until a named person, anyone with a role, or a user from the event approves or rejects in the Approvals inbox. Connect the Approved and Rejected ports to the steps that should follow. A workflow can also wait until something happens, for example until an invoice is paid, or until a time limit passes, and then take the matching path.

Not every workflow needs an event. The On a schedule trigger runs hourly, daily, weekly or monthly in the company time zone. On a date starts the workflow a set number of days before or after a date on a record, such as three days before an unpaid invoice is due. Nothing happened starts it when a record stays in a status, or when a store has no sale by 11:00 on a weekday. Run manually adds a Run now button for jobs people start themselves.

Webhook and API action hygiene

Send webhook actions should target HTTPS endpoints with idempotent receivers because steps are retried after failures. Each webhook is HMAC-signed, so receivers can reject requests that did not come from Biznsbook. Log audit actions complement webhooks when you need an internal record without external dependencies.

Templates speed up setup — the gallery shows only templates whose modules your company uses. Start from a template, rename it, adjust the conditions, and test it before activation. Save a pattern you reuse as a company template.

Production promotion checklist

Before activating a workflow that sends customer email, run a test with your own address and confirm unsubscribe and branding meet policy.

Document the workflow owner and intended trigger in the workflow description so future admins know why cooldown and priority were set. Builders cannot activate their own workflows; Save & request activation sends the change to an Automation Manager.

Monitoring and failure recovery

Review failed runs weekly. A run fails when a downstream API times out or validation fails — ignoring the Runs page means leads never get follow-up email even though the workflow shows as active. Open the run, read each step's input and output, and use Show path on canvas to see where it stopped.

If a workflow keeps failing, the circuit breaker switches it off. Fix the cause before an Automation Manager or Operator switches it back on, and set daily limits on high-volume triggers during data migrations.

Naming and change management

Prefix workflow names with module and outcome — CRM-Lead-Notify-Sales — so administrators can audit fifty active rules without opening each one. Rename workflows when business logic changes; cloning without retiring old rules duplicates emails customers complain about.

Export a workflow as JSON before a large change so you can import the old version as a draft if needed, and keep a change log entry when activating workflows that touch customer communications.

Metrics to track monthly

  • Active workflows with success rate above 95%
  • Failed runs awaiting retry on the Runs page
  • Lead created automations with measured response time
  • Stock low alerts converted to purchase requisitions
  • Daily run limit breaches

Start with three metrics; trend direction matters more than a single point-in-time snapshot.

Manual follow-ups vs Biznsbook Automation

Compare running this by hand with Biznsbook 190+ event triggers and related capabilities.

CapabilityManual / SpreadsheetBiznsbook
Trigger model❌ Manual checks and polling✅ 190+ business events, schedules, a date on a record, a nothing-happened check, or Run now
Builder❌ Code or scripts✅ Visual canvas with IF/ELSE branches
Actions❌ Email only✅ Email, task, webhook, WhatsApp, approval
Who switches it on❌ Anyone with script access✅ Automation Manager role
Testing❌ Try it live✅ Dry run that shows the path
Failure handling❌ Silent drop✅ Run history, retry and circuit breaker

First workflow pattern

Ship one production workflow — Lead created with a single create-task action — before adding webhooks or branches; check its success rate on the Runs page for a week, then layer conditions. Pause workflows before bulk data imports that mass-update statuses — imported rows can fire hundreds of events and flood webhooks in a single hour.

Write this into your automation runbook and revisit it when you add workflows, roles or modules.

Frequently asked questions

Which CRM triggers exist?

CRM triggers include lead created, lead assigned, lead converted, deal stage changed, deal won and deal lost, plus activity and task events. The builder lists every trigger for the modules you use.

Can inventory trigger replenishment?

Stock low can drive notifications, tasks or webhooks; pair it with the replenishment process your team defines.

What is send webhook?

Send webhook posts a JSON payload describing the event to a URL you choose. Each request is HMAC-signed so the receiver can check it came from Biznsbook.

Who can activate a workflow?

Only an Automation Manager. Automation Builders build and test drafts and use Save & request activation, which emails the managers.

Can HRMS events trigger workflows?

Yes. HRMS triggers include employee onboarded, leave requested and leave approved; pair them with send notification or create task actions for HR operations teams.

What about Real Estate events?

Real Estate publishes booking created, booking confirmed, installment overdue and rent overdue among others — useful for leasing follow-up automations.

Can an invoice, a till sale or a batch start a workflow?

Yes. Invoice paid, invoice overdue (day 1, 7, 14 or 30), a supplier bill paid, a closed accounting period, a POS sale, refund or closed till, a fully received stock transfer, a batch 30, 14, 7 or 1 days from expiry, a failed Toast sales import, an expense reimbursement and a completed field job are all triggers. The builder lists the ones your modules license.

Can one workflow do different things for different records?

Yes. Add an IF/ELSE step: records that match the condition follow the Yes path and the rest follow the No path. A Request approval step works the same way, with Approved and Rejected paths.

Can a workflow run without an event?

Yes. Use On a schedule to run it hourly, daily, weekly or monthly, On a date to start a set number of days before or after a date on a record, Nothing happened when a record stays in a status or a store has no sale by 11:00 on a weekday, or Run manually so someone starts it with Run now.

How this differs by industry

Retail

Retail CRM teams create a follow-up task when a web-form lead is created, while a Stock low workflow notifies buyers about top-selling SKUs.

Wholesale & distribution

Distributors send a signed webhook to their purchasing tool when key depot SKUs hit Stock low, and email the account manager in the same run.

Manufacturing

Plants notify the spare-parts team when a deal is won and raise a task when a quality inspection fails on a work order.

More guides: Build a Repeatable Sales Process, Automate Sales Workflows, Start Automation Workflows from Templates, Add Approval Steps to Workflows, Build a Landing Page with a Free Download, Schedule Recurring Workflows.