Your first automation

Small, boring, and yours

Your first automation should be almost embarrassingly simple: two steps, low stakes, something you actually do every week. Not because you can't handle more — because the skill you're building today isn't complexity, it's the build ritual: trigger, action, map, test, name, watch. Once that ritual is in your hands, a ten-step workflow is just the ritual repeated.

Our example build: "When someone fills my contact/interest form, add a row to my spreadsheet and email me." Swap in your own starred task if it's this shape — anything of the form new thing arrives → record it → tell me.

The build ritual, step by step

1. Pick the trigger app and event. In Zapier or Make, choose your form tool, then the event "new submission/entry." The platform will ask you to connect the account (a login-and-allow screen — this is normal, and you can revoke it anytime in that app's settings).
2. Feed it a real sample. Submit your own form once with obvious test data ("TEST — Sera, test@…"). The platform pulls that submission in so you can see exactly what data the trigger carries. Never build against imaginary data.
3. Add the action. Choose your spreadsheet app → "create row." Now comes the one genuinely new skill:

Field mapping (the mail-merge of automation)

The action step shows your spreadsheet's columns; the trigger offers its fields as little tokens (name, email, message, date). You drag or pick which token fills which column — Name → column A, Email → column B. That's field mapping, and it's the whole game. If a downstream column shows up blank later, the mapping is where you look first.

4. Test the action. Run the step; go look at the actual spreadsheet. A row with your test data should exist. If yes — you've automated something. If no, read the error out loud; nine times out of ten it names the field that's empty or the account that needs reconnecting.
5. Add the second action (email or Slack to yourself: "New form entry from {name}"). Map the fields the same way.
6. Name it like an adult and switch it on. "Form → Sheet + notify (built July 2026)". Future-you, staring at a list of automations at midnight, will be grateful.

The first-week watch

An automation isn't done when it works once — it's done when it's survived a week of real life. For the next seven days: let it run, but keep doing your quick manual glance. You're watching for the edges — the submission with an empty field, the duplicate, the weird character that breaks a column. After a clean week, cross the task off your list for good and feel the specific joy of a chore that no longer exists.