How to Start Automation Workflows from Templates

Why automation projects stall at the blank page

Most teams know what they want automated: tell a manager when an expense needs approval, assign new leads, warn when stock is low. Faced with a blank workflow builder, though, they are unsure which event to choose, what conditions to set and how to test it without emailing customers by mistake.

So the automation either never gets built, or one enthusiastic person builds something complicated that nobody else understands. When it starts failing quietly, nobody notices until a customer or employee complains.

Templates give a working starting point for common jobs. Combined with testing before activation, a run history, and an alert when a workflow switches itself off, they let a small team run automation safely without a specialist.

Why this happens

• Building every workflow from a blank canvas.
• Activating without testing.
• No one watching the run history.
• Failing workflows switch off unnoticed.
• Workflows built for modules the company does not use.

Biznsbook addresses this through automation templates, workflow testing before activation, automation panel on record pages, alerts for auto-disabled workflows in Business Automation, reacting to events the rest of Biznsbook publishes.

Small gaps in automation rarely fail loudly. They show up later as numbers nobody can explain. Recording each step where it happens removes the guesswork.

Step-by-step: Start Automation Workflows from Templates

Written for operations, sales and finance teams setting up no-code workflows in Biznsbook Business Automation.

1. Open the template library. Go to Automation → Templates. The library fills itself the first time you open it.
2. Browse and preview. Browse by category or search, and open Preview to see the steps.
3. Use the template. Choose Use template. A copy is created for your company, only for modules you have licensed.
4. Adjust it. Change recipients, wording and conditions to match your process.
5. Test, then activate. Save it (new workflows start inactive) and press Test. It shows whether the workflow would start, how each condition evaluated and what each step would receive; nothing is sent or changed. Then activate it.
6. Watch the runs. Automation → Runs shows every run with its step-by-step detail; Workflows shows totals, today's runs and success rates.
7. Get alerted if it switches off. A workflow that keeps failing is switched off and labelled Auto-disabled. Build a workflow on the event Workflow Disabled Automatically that emails or notifies you.

Review results after the first full monthly 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: Building every workflow from a blank canvas. Repeating this each month usually shows up first in workflows that fail quietly.
• Mistake 2: Activating without testing. Repeating this each month usually shows up first in workflows that fail quietly.
• Mistake 3: No one watching the run history. Repeating this each month usually shows up first in workflows that fail quietly.
• Mistake 4: Failing workflows switch off unnoticed. Repeating this each month usually shows up first in workflows that fail quietly.
• Mistake 5: Workflows built for modules the company does not use. Repeating this each month usually shows up first in workflows that fail quietly.

Each of these turns into a question the team cannot answer quickly. Fix the process on the record rather than in email threads or spreadsheets.

Best practices that hold up as you scale

• Open the template library — Go to Automation → Templates.
• Browse and preview — Browse by category or search, and open Preview to see the steps.
• Use the template — Choose Use template.
• Adjust it — Change recipients, wording and conditions to match your process.
• Test, then activate — Save it (new workflows start inactive) and press Test.

Start from a template, test before you activate, and give every workflow a name that says what it does.

How Biznsbook supports this workflow

automation templates is part of Biznsbook and works on the same records as the rest of automation, so the decision, the stock and the books stay in step and every action is recorded with who did it and when.

workflow testing before activation is part of Biznsbook and works on the same records as the rest of automation, so the decision, the stock and the books stay in step and every action is recorded with who did it and when.

automation panel on record pages is part of Biznsbook and works on the same records as the rest of automation, so the decision, the stock and the books stay in step and every action is recorded with who did it and when.

alerts for auto-disabled workflows is part of Biznsbook and works on the same records as the rest of automation, so the decision, the stock and the books stay in step and every action is recorded with who did it and when.

Automation needs the Business Automation licence; triggers and templates appear only for modules your company licenses.

Suggested implementation timeline

1. Week 1: Set up automation templates and the permissions the people involved need.
2. Week 2: Run the real process in Biznsbook only, with no side spreadsheet, for one team or site.
3. Week 3: Review what was recorded with the people involved and tighten the rules where they disagreed.
4. Month 2: Roll out to every team or site.
5. Ongoing: Reviewing workflows each month.

Related guides

Cluster hub: CRM & sales guides. Also see event-driven workflows and delayed triggers.

How templates relate to events and workflows

Every workflow starts from an event that another module publishes, such as a new lead, a submitted expense or low stock. Automation → Events lists every event you can trigger on, its fields, how often it happened in your company and when it last happened. Events marked Not yet emitted are registered but nothing raises them yet, so a workflow on them will not run.

A template is a ready-made workflow on one of those events. After Use template it is an ordinary workflow: you can open it in the visual canvas or the simple builder, add conditions, delays or more actions, and it appears in Workflows with its own totals and success rate.

Automation needs the Business Automation licence, and the modules whose events you use. Keep the number of active workflows small and named after what they do, so the run history stays readable and a failing workflow is easy to find.

Reading the run history and fixing failures

Automation → Runs lists every run. Filter by workflow, status (including Waiting, Partly completed and Timed out), dates, record number, or only runs with errors, and jump to a workflow's runs or failures from its row. Viewing runs needs the View logs permission.

Expanding a run shows each step's result, input, output and error, the event data that started it, and the version of the workflow it used. That is usually enough to see whether a condition was wrong, a field was empty, or an email address was missing.

For a failed, partly completed or timed-out run, Retry continues from the first step that did not succeed, and finished steps are not repeated, so customers are not emailed twice. Cancel stops a run that has not started or is still waiting on a delay. Run history is kept for 90 days by default.

Templates that send email sequences, such as lead drip enrolment, also need Communication Center and an email drip sequence with timed steps. Due emails go out automatically and are checked every 30 minutes.

Metrics to track monthly

• Active workflows and their success rates
• Auto-disabled workflows this month
• Runs per workflow per week
• Events with no workflow yet

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

Manual workarounds vs Biznsbook

Compare common manual workarounds with Biznsbook automation templates and the related capabilities.

Reviewing workflows each month

Once a month, open Workflows and sort by success rate. Check any Auto-disabled workflow in Runs, fix the cause and reactivate it, retire workflows nobody relies on, and look at Events for activity you are not yet using. Before changing an active workflow, test the new version first: the test always checks the saved version, so save, test, then activate. Record the change in the workflow name or notes.

Write down who owns each workflow and review them together each month.

Frequently asked questions

How this differs by industry