lesson
25 min

Triggers, Actions, Filters, and Mapping

Learn the four building blocks that every automation tool shares.

Objective

By the end of this lesson, you can explain triggers, actions, filters, and field mapping, and spot each one in a working automation.

The same blocks in every tool

Zapier, Make, and n8n look different. Under the hood, they use the same four blocks.

  • Trigger. The event that starts the automation. "New form response." "New email with the label Catering." "Every Monday at 8 a.m."
  • Action. Something the automation does. "Add a row to a sheet." "Send an email." "Create a calendar event."
  • Filter. A rule that lets the automation continue only if a condition is true. "Only continue if guest count is more than 20."
  • Field mapping. Telling the action which piece of data goes where. "Put the form's Name answer in column A of the sheet."

Zapier calls an automation a Zap. Make calls it a scenario. n8n calls it a workflow. Same idea.

A local example: a Saturday food drive

A neighborhood association on the East Side runs a monthly food drive. Volunteers sign up with a Google Form.

BlockSetting
TriggerNew Google Form response
Action 1Add a row to the "Volunteers" sheet
FilterOnly continue if the shift is "Saturday morning"
Action 2Send a confirmation email with the parking map
MappingForm "First name" goes into the email greeting. Form "Email" goes into the To field

Notice the filter. Volunteers for other shifts get a different email, or none yet. Filters keep an automation from doing the wrong thing to the wrong person.

Data moves as fields

When a trigger fires, it carries data in fields. A field is one labeled piece of information, like "first_name" or "phone." Each later step can use those fields.

This is the most common place beginners get stuck. If the email greeting says "Hi ," with a blank, the mapping is wrong or the field was empty.

See it in code

You will not write code in Zapier or Make. But seeing the logic as code makes it clear. Here is the food drive automation as a few lines of JavaScript. Change the sample sign-up and run it.

Trigger, filter, action

Change the shift to 'Sunday afternoon' and run it again. Then remove the first name and see what the email says. Keyboard users: press Esc, then Tab, to leave the editor.

Loading the code editor...

Press Esc, then Tab, to move focus out of the editor.

Notice the line that checks for a missing name. Good automations plan for missing data. You will do much more of this in Module 5.