Automate a repetitive task

Automation lets software carry out steps when something happens. A trigger starts the workflow. An action does something, such as adding a row or sending an email. A condition decides whether to continue or take a different route.

Not every automation needs AI. Moving a form response into a spreadsheet can use ordinary rules. AI may help classify a free-text request, but then you need checks for misclassification. Start with the reliable rule-based part.

This page is a worked plan and practice exercise. It is not connected to a form, spreadsheet or email service and does not send messages.

A community organiser receives workshop registrations. Instead of copying each response manually, they want to record it and acknowledge receipt. An acknowledgement is not a guaranteed place or payment receipt.

This is field mapping: deciding where each piece of information goes. The example.com address is for planning only. For a live test, use an inbox you own and have permission to test.

Add status and processed_at columns. Store only the information the process needs; a registration does not need a date of birth or identity document by default.

Zapier connects apps through workflows often called Zaps. Make uses visual workflows called scenarios. n8n uses connected nodes and offers hosted and self-hosted options. Self-hosting requires maintenance and security work; it is not automatically a free or simpler choice.

Start with the tool that supports your existing apps and the workflow steps you need. Check current plan limits, connection permissions and task or credit costs. This three-step example may exceed a particular free plan’s capabilities. Official links and access notes.

An API is a way for software to request data or actions from another system. A webhook is a message one system sends when an event occurs. Many beginner connectors handle these details for you; never paste secret credentials into a public prompt.

1. Prepare: create a test form and a test spreadsheet in tools you control. Use only the fields above. Keep the workflow disabled while setting up.
2. Choose the trigger: select the form app and its new-submission event. Connect only the necessary account permissions. Retrieve one test submission.
3. Validate: require a name, a plausible email and an allowed session value. Missing information should stop for review, not continue blindly.
4. Record: add a spreadsheet action. Map each response field to its matching column. Test this step and inspect the actual row.
5. Acknowledge: add an email action. Map the submitted email to the recipient, use an authorised sender and a fixed message. During testing, override the recipient with your own inbox.
6. Inspect the run: check the row and the actual received message. Then review errors and duplicates before considering activation.

Exact labels depend on the connector. Start with the vendor’s first-workflow guide or Zapier quick-start guide if you need help with its interface. You can complete this lesson entirely on paper without connecting accounts.

Walk these events through your diagram, or use a disabled test workflow with your own inbox. Record what happened at each step.

• Valid TEST-001: one row and one acknowledgement.
• No email: no email attempt; mark for review.
• Same TEST-001 again: no duplicate row or message.
• Spreadsheet permission removed: stop and notify the operator; do not pretend the registration was recorded.
• Email step fails after the row was saved: retain the row, record the failed status and retry only the missing step after inspection.

Monitor run history after activation. Set an owner for errors and check that quotas, tokens and connections remain valid. Do not put private response content into unnecessarily broad logs or alerts.

A filter can allow only valid session requests to continue. A lookup can check whether the submission ID has already been processed. The ID should identify the submission event; email alone may wrongly block a legitimate second request.

Keep a human involved when a step involves money, access rights, sensitive complaints, ambiguous information or irreversible consequences. If the process changes every week, stabilise it before automating it.

For your exercise, map one repetitive task you know. Name the trigger, fields, actions, failure owner and stop condition. Test three fictional cases. If you cannot describe what should happen when a field is missing, the workflow is not ready.