• Practice
  • About 15 min
  • 5 practice questions

Workflow automation: triggers, actions and keeping a person in charge

Break a repetitive task into trigger and action, judge whether it is worth automating, set up simple automations such as email sorting, reminders and form responses to a sheet, test them, and keep a person approving anything sent out.

If something looks wrong, please tell us.

By the end of this lesson you can

  • Describe any automation as a trigger, optional conditions and actions.
  • Work out whether a repetitive task is worth the time it takes to automate.
  • Test an automation safely and decide where a person must approve before anything goes to others.

A lot of office time goes into small repeated steps: moving emails into folders, copying form answers into a register, sending the same reminder every week. Automation lets a computer do such steps on its own. AI tools help here too: they can explain options, suggest the steps and write a simple macro or rule. The thinking skill underneath does not change from tool to tool, and that is what this lesson teaches.

Trigger, condition, action

Every automation can be written as When something happens (the trigger), if certain conditions hold, then do something (the action). Writing a task this way on paper first makes it clear whether it can be automated at all.

Every automation

  1. When: trigger Something happens.
  2. If: condition Certain conditions hold.
  3. Then: action Do something.
Automations written as trigger, condition, action
TriggerConditionAction
A new email arrivesThe subject contains 'Invoice'Move it to the Accounts folder
Every Monday at 9 a.m.NoneSend yourself a reminder to update the weekly register
Someone submits a formNoneAdd the answers as a new row in a spreadsheet
A new row is added to the sheetThe 'Urgent' column says YesNotify the section in-charge

Kinds of tools

Several well-known kinds of tool can do this. Email rules or filters sort incoming mail by sender or subject. Macros, built into many spreadsheet and word-processing programs, record or script a series of steps and replay them. Many online form tools can send responses straight into a spreadsheet. No-code automation services - Zapier, Make and Microsoft Power Automate are well-known examples - connect different apps with trigger-and-action steps. Features and names differ between products and change over time, so describe what you need in trigger-action terms and then look for how your own tool does it.

Worked example 1: is it worth automating?

A clerk spends 10 minutes every working day copying form responses into a register, 5 days a week: 10 × 5 = 50 minutes a week. Setting up and testing an automation would take about 3 hours = 180 minutes. Time to pay back = 180 ÷ 50 = 3.6 weeks, so after about four weeks the automation is saving time. A task done twice a year for 5 minutes would never repay 3 hours. Good candidates are frequent, rule-based and boring; poor candidates need judgement each time or change often. (Times are illustrative.)

Automate what is frequent, repetitive and rule-based. Test before you trust. A person approves anything that goes to other people.

Worked example 2: form responses to a sheet, tested

  1. Write it out: when a training-registration form is submitted, add a row to the sheet; if 'Needs accommodation' is Yes, email the in-charge.
  2. Build it on a test copy of the sheet, not the live register.
  3. Submit three test entries yourself: a normal one, one with accommodation Yes, and one with a field left empty.
  4. Check each result by hand: right columns, no duplicate rows, the email sent only for the Yes entry, nothing broken by the empty field.
  5. Only then switch it to the real sheet, and look at the results daily for the first week.

Testing matters because automations repeat mistakes faithfully. A wrong email rule can hide important messages in a folder no one opens; a wrong condition can send the same message a hundred times. A small test with known inputs, checked by hand, catches this before it reaches real work.

Keep a person approving

Automating internal, reversible steps - sorting, copying, reminding yourself - carries little risk. Anything that goes to other people is different: replies to citizens, letters, payment or approval messages, posts on social media. Set these up so the automation prepares a draft and a person reviews and sends it. An AI-written reply sent automatically can state a wrong date or promise something the office cannot do, in the office's name.

Who sends what

  • Internal and reversible: little risk
    • Sorting
    • Copying
    • Reminding yourself
  • Goes to other people: a person approves
    • Replies to citizens and letters
    • Payment or approval messages
    • Posts on social media
    • The automation prepares a draft; a person reviews and sends it

Safety with automations

  • Give an automation service only the access it needs, and follow your office's IT policy on which tools are approved.
  • Do not enable macros in files that arrive from unknown senders: macros are programs and can carry malware.
  • Never put passwords or OTPs into a shared automation or an AI prompt.
  • Write down what each automation does and who owns it, so it can be switched off when a process changes.

Key takeaways: write the task as trigger, condition, action; automate frequent, rule-based work whose setup time pays back; build on a copy and test with known inputs; keep a person approving anything sent to others; grant minimum access and never enable macros from unknown files.

Check your understanding

  1. 1. In the automation 'When a new email arrives, if the subject contains Invoice, move it to the Accounts folder', what is the trigger?

    1. Moving the email to the Accounts folder
    2. The word Invoice in the subject
    3. The Accounts folder
    4. A new email arriving
    Show answer

    Answer: D. The trigger is the event that starts the automation: a new email arriving. The subject check is the condition and moving the email is the action.

  2. 2. A task takes 6 minutes a day, 5 days a week. Automating it takes 2 hours to set up. Roughly how many weeks until it pays back?

    1. 2 weeks
    2. 4 weeks
    3. 10 weeks
    4. 24 weeks
    Show answer

    Answer: B. Time saved per week = 6 × 5 = 30 minutes. Setup = 2 hours = 120 minutes. Payback = 120 ÷ 30 = 4 weeks.

  3. 3. Which task is the poorest candidate for automation?

    1. Moving every email from a known supplier into one folder
    2. Adding each form response as a row in a sheet
    3. Deciding how to reply to a citizen's unusual complaint
    4. A weekly reminder to update the attendance register
    Show answer

    Answer: C. A reply to an unusual complaint needs judgement every time. The others are frequent, rule-based steps that suit automation.

  4. 4. An office sets up AI to draft replies to public queries. What is the safest arrangement?

    1. The AI sends replies at once so citizens are not kept waiting
    2. The AI prepares drafts and a staff member reviews and sends each one
    3. Replies are sent automatically and checked once a month
    4. Only replies longer than 100 words are reviewed
    Show answer

    Answer: B. Anything sent to other people in the office's name is reviewed by a person first, because an automatic reply can state wrong facts or make promises the office cannot keep.

  5. 5. A spreadsheet from an unknown sender asks you to 'enable macros to view the content'. What should you do?

    1. Do not enable macros; report or delete the file as your office's policy says
    2. Enable macros, since spreadsheets are always safe
    3. Forward it to colleagues to see if it opens for them
    4. Enable macros but close the file quickly
    Show answer

    Answer: A. Macros are small programs and can carry malware. Files from unknown senders that ask for macros to be enabled are a common attack, so they are not enabled.

Privacy · Terms · Refunds · Delivery