Course A · Module A3 No-Code Automation · Lesson 7 of 17

Triggers & Actions

Every automation ever built — from a Fortune 500 pipeline to a two-step Zapier zap — is the same two-word sentence.

~10 min · No account needed yet · Prereq: A3 (your chosen task)

You're about to enter the most practical module in the course. But before you build anything, you need to understand the one grammar rule behind every automation in existence: when X happens, do Y. That's it. Every workflow tool, every no-code platform, every elaborate pipeline is just variations on that sentence. This lesson's single win: once you see the pattern, you'll be able to look at any repetitive task in your business and immediately sketch an automation for it.

Trigger: the "when X happens" half

A trigger is the event that wakes your automation up. Nothing runs until the trigger fires. Think of it like a motion-sensor light — the light doesn't care about logic; it just waits for movement.

Until there's movement (the trigger), nothing happens. The moment there is, the automation runs.

New emailA message arrives in a specific inbox or matches a filter.
Form submittedSomeone fills out a Typeform, Google Form, or website contact form.
New spreadsheet rowA row is added to a Google Sheet or Airtable base.
Calendar eventA meeting is booked, cancelled, or starts in X minutes.
ScheduleEvery day at 9 am, every Monday, the first of the month.

Action: the "do Y" half

An action is what the automation does the moment the trigger fires. With AI in the loop, your actions can do much more than route data — they can think about it first.

SummarizeTake a long email or document and pull out the key points.
Draft a replyWrite a first-pass response in your tone and send (or queue) it.
ClassifySort an item into a category — "urgent / not urgent", "lead type", "topic".
Add to a sheetWrite structured data (name, summary, label) into a spreadsheet row.
Post to SlackSend a message to a channel — "New lead: [name], interested in [product]."
Send an emailFire off a reply, notification, or follow-up automatically.

Connecting two apps with no code

Tools like Zapier and Make are the plumbing. They connect thousands of apps — Gmail, Slack, Sheets, Notion, Typeform, Stripe — without you writing a line of code. You pick a trigger app, pick an action app, and draw the connection. That's a zap (Zapier) or a scenario (Make).

Zapier

  • Largest app library (7,000+)
  • Easiest for first-timers
  • Free tier: 100 tasks/month
  • Best for: simple 2-step automations

Make (formerly Integromat)

  • Visual flowchart builder
  • More powerful multi-step logic
  • Free tier: 1,000 operations/month
  • Best for: branching, loops, complex flows
Start with a template. Both Zapier and Make offer hundreds of ready-made automation templates. Instead of building from a blank screen, browse templates for your trigger app (e.g. "Gmail") and pick the one closest to your use case. Modify the prompt inside it. You'll ship something working in under 30 minutes the first time.

A template end to end

Here's what a simple automation looks like, written as a plain-English sentence first, then mapped to the tool:

Plain-English version:
  1. Trigger: A new row is added to my "Leads" Google Sheet.
  2. AI action: Summarize the lead's notes in one sentence and classify them as "hot / warm / cold" based on what they wrote.
  3. Output action: Post a Slack message to #sales with the name, classification, and one-sentence summary.

In Zapier, that's three steps. Step 1 is the trigger (Google Sheets — New Row). Step 2 is an AI action (Zapier's built-in ChatGPT/Claude action, or a webhook to the model of your choice). Step 3 is the output action (Slack — Send Channel Message). You filled in no code — only your prompt, your sheet columns, and your channel name.

Check yourself

Answer before opening. Recalling it now is what makes it stick.

What is a trigger? Give an example from your own business.

A trigger is the event that starts the automation. Common examples: a new form submission from your website, a new row added to an order tracker, an inbound email to your support address. It's the "when X happens" half — nothing runs until this event fires.

Your automation should draft a reply every time a contact form is filled out. What's the trigger and what's the action?

Trigger: new form submission. Action: AI drafts a reply (and optionally sends it or queues it for review). The trigger watches the form; the action does the work. Keep them separate in your head and building the zap becomes obvious.

Why start from a template rather than a blank automation?

Templates give you a working skeleton — trigger, action, and field mappings already wired up. You customize the AI prompt inside rather than making all the connection decisions yourself. Faster, and far fewer first-run errors.

Read this next (primary source)

Zapier Resources & Learning Center. The "How Zapier Works" guides explain trigger-action workflows with real app examples. Browse the resources matching your trigger app. See RESOURCES.md for more.

I'm your teacher — describe your task. Tell me the recurring task you picked in A3 — what kicks it off, what you do, where the result ends up — and I'll map it to a trigger, an AI action, and an output action. You'll have a blueprint to build from in A8.

Terms introduced this lesson — trigger, action, automation, no-code tool — are all in the course glossary.