Home / Guides

Automation glossary for small business owners

Plain-English glossary of workflow automation terms: trigger, webhook, API, n8n, RPA, LLM and more, with small-business examples.

By Paras, Evenstead Automation, Edmonton · Last updated

Disclosure: I run Evenstead Automation, so some of these definitions use our own products as examples. Where a term means something specific in our work, I say so.

When you read a proposal, a software page or a forum thread about automation, the same dozen terms come up. They sound harder than they are. This glossary explains each one in plain words, with a small-business example. If you are choosing help, the automation readiness checklist is a good next step.

The basics

Workflow

A workflow is a sequence of steps for one job. “When a quote is sent, wait two days, check for a reply, send a short note if there is none” is a workflow. You can run a workflow by hand with a calendar, or let software run it. For a longer explanation, see workflow automation in Edmonton.

Automation

Automation means a workflow runs without someone starting each step. It does not mean nobody is in charge: good automation still has an owner who sets the rules and reads the results.

Trigger

The event that starts a workflow: a form is submitted, a call is missed, an invoice passes its due date, a calendar booking is made.

Action

A step the workflow takes after the trigger: send a text, add a row, create a task, notify you.

Condition (or filter)

A rule that decides which path to follow. “If the customer replied, stop. If not, send the next note.” Conditions are what make a flow polite instead of annoying.

Delay (or wait step)

A pause built into the flow, such as two days between messages. Most follow-up schedules are triggers, delays and conditions arranged in a row.

How tools talk to each other

Integration

A ready-made connection between two tools, for example your calendar and your messaging tool. If an integration exists, setting it up is usually a matter of signing in and choosing options.

API

The official way one piece of software lets another read or change its data. You do not have to use one directly. It matters when a tool you rely on has no ready-made integration and somebody has to connect it by hand.

Webhook

A web address that one tool calls to say “something just happened.” It lets a flow start the moment an event occurs instead of checking every few minutes.

CRM

Customer relationship management: the place where you keep your customers, leads and notes. For a small shop it may be a spreadsheet, and that is fine. A flow needs to know where its list lives.

The tools you will hear named

Zapier and Make

Hosted automation tools with free tiers and paid plans. You build flows by joining blocks on a screen. Our Zapier vs Make vs n8n comparison explains when each suits a small shop.

n8n

A workflow tool that can be self-hosted or used as a hosted service. We build in n8n for clients who want to own their flows. See n8n automation in Alberta and the n8n security checklist.

RPA

Robotic process automation: software that clicks through screens the way a person would, used where a system has no integration. Many small-business jobs never need it. The comparison guide covers the difference.

Language-model terms

Large language model (LLM)

The kind of software behind chat assistants. It reads text and writes text. In a small-business flow it is used for narrow jobs, such as sorting an inquiry into a category or drafting a reply for you to approve.

Prompt

The written instructions given to a language model. Clear instructions, plus examples of good replies, are most of what makes a flow behave well.

Hallucination

When a language model states something that is not true as if it were. This is why we design flows so prices, dates and promises come from your own information or go to you first, rather than being written by the model. Our page on what AI can and cannot do for a small shop goes further.

Human-in-the-loop

A person approves the step before it happens. In our follow-up and reminder products, the owner approves the message wording before anything goes out. Our phone and chat assistants work from information the owner approves, and cases they are not set up to handle are passed to the owner.

Terms we use in our own work

Safe mode (test mode)

Our name for running a flow so that it only shows what it would have sent, to you, and sends nothing to customers. A flow stays in safe mode until you have seen real examples and said go.

Handover

A one-page sheet describing what the flow does and how to pause it, plus your templates and data, which you keep if you stop working with us. The goal is that you can understand and maintain it. See how we run projects.

Fit session

A short call to see whether a flow makes sense for your business before anything is built. Details are here.

Messaging rules in one line each

These terms come from Canada's anti-spam law (CASL). Read the sources and the CASL guide rather than relying on a glossary line, and treat this as general information, not legal advice.

Consent

Permission to send a commercial message, either express (they said yes) or implied (for example, an inquiry from them in the last six months, or a purchase in the last two years). The detail matters, so check the guide.

Opt-out (unsubscribe)

A working way for the person to say stop. CASL requires one in every commercial email or text, automated or not, along with who is sending it and how to reach them, and the request must be honoured within 10 business days. Good practice is to stop right away.

Where to go next

If a term here is blocking you from understanding a proposal, send it to us and we will explain it for free. The 10-minute missed revenue audit is a practical first step, and the fit session is where we look at your own business.

This is general information, not legal advice.

Questions people ask

What is workflow automation in simple words?

It is a set of steps that run on their own when something happens, such as a new inquiry arriving, a quote reaching day five, or an invoice going overdue. You decide the steps once, and the software repeats them the same way each time.

What is the difference between a trigger and an action?

A trigger is the event that starts a flow, like a form submission or a missed call. An action is what the flow then does, like sending a text, adding a row to a sheet or telling you about it. Most flows are one trigger followed by a few actions.

What is a webhook?

A webhook is a web address one tool calls to tell another tool that something just happened. Your booking form can call a webhook the moment someone submits it, so the next step starts at once instead of waiting for someone to check.

What does human-in-the-loop mean?

It means a person approves a step before it goes out. In our follow-up and reminder products, the owner approves the message wording before anything goes out. Our phone and chat assistants work from information the owner approves, and cases they are not set up to handle are passed to the owner.

Do I need to learn any of these terms to use automation?

No. You need to know what you want to happen and who should approve it. The terms matter mainly so you can read a proposal and ask good questions before you sign.

Where can I read about the Canadian rules for automated messages?

Start with our plain-language CASL guide, which links to the source pages, and use the message checklist before you send. It is general information, not legal advice.