Hands-On Activity & Quiz (Continued)
Part 5: Build Your Automation in Make
Step 3: Add action module (10 minutes)
- Click “+” after trigger module
- Search for action app
- Choose action
- “Create” actions are common
- Select what you want to do
- Connect account
- Click “Add” next to Connection
- Sign in and authorize
- Map fields
- Click in field
- Click icon to browse trigger data
- Select appropriate data from trigger
- Visual mapping interface
- Test
- Click “OK”
- Right-click → “Run this module only”
- Check destination app to verify
Step 4: Activate (5 minutes)
- Save scenario
- Click “Save” (bottom left)
- Name it clearly
- Schedule
- Click clock icon (bottom)
- Choose frequency (Every 15 minutes, hourly, etc.)
- For most: Every 15 minutes works well
- Turn ON
- Toggle switch at bottom left
- Scenario is now active
- Test in real life
- Trigger it manually
- Verify it works
- Check execution log (shows what happened)
Part 6: Monitor & Verify (10 minutes)
Whether you used Zapier or Make:
Day 1 – Immediate testing:
- Trigger automation manually 2-3 times
- Verify each action occurs correctly
- Check data is mapping properly
- Make adjustments if needed
Week 1 – Daily checks:
- Review automation history each day
- Look for errors or failures
- Verify it’s running when expected
- Tweak settings if needed
Note any issues:
- What worked perfectly: ___
- What needed adjustment: ___
- Errors encountered: ___
Part 7: Reflection & Planning (10 minutes)
Answer these questions:
1. Automation experience:
Setup difficulty (1-10, where 10 is very easy): ___
What was confusing?
What was easier than expected?
Is your automation working?
- Yes, perfectly
- Mostly, with minor issues
- Not yet, still troubleshooting
- No, need to start over
2. Value assessment:
Time this automation will save per week: ___
Time this automation will save per year: ___
How does it feel to have this automated?
Would you create another automation?
- Definitely
- Probably
- Maybe
- No, this was enough
3. Next automation ideas:
Based on what you learned, what else could you automate?
Automation idea 2:
- Trigger: ___
- Action: ___
- Apps needed: ___
Automation idea 3:
- Trigger: ___
- Action: ___
- Apps needed: ___
Which tool will you use going forward?
- Zapier (easier for me)
- Make (prefer the features/pricing)
- Both, for different purposes
- Still deciding
4. Integration with other tools:
Could this automation work with your:
- NotebookLM workflow
- Notion workspace
- Trello boards
- Other tools from this course
How?
5. Limitations encountered:
Did you hit any of these free tier limits?
- Task/operation limits
- Number of Zaps/scenarios allowed
- Features you wanted but need paid plan
- No limitations yet
If you hit limits, what’s your plan?
- Upgrade to paid plan (worth it)
- Optimize automation to use fewer tasks
- Accept the limits for now
- Switch to different tool
Part 8: Optimization (Optional – 10 minutes)
If your automation is working, try enhancing it:
Add a filter:
- Only run if certain condition is met
- Example: Only if email subject contains “Invoice”
- Saves tasks, makes automation smarter
Add another action:
- What else should happen?
- Chain multiple actions together
- Example: Create task AND send notification
Add error handling:
- What if something fails?
- Send yourself notification
- Create fallback action
Test edge cases:
- What if field is empty?
- What if format is different?
- Does it handle unusual data?
Congratulations! You’ve:
- ✅ Learned what automation is and why it matters
- ✅ Understood Zapier vs. Make
- ✅ Built a working automation
- ✅ Tested and verified it works
- ✅ Planned future automations
- ✅ Completed Phase 3: Get Organized!
Keep this automation running! Monitor it for a week, then move on to your next automation. Build your automation library one workflow at a time.
3 Quiz Questions with Answers
Question 1
What is the basic structure of every automation?
A) App → Tool → Result
B) Trigger → Action(s)
C) Input → Process → Output
D) Start → Middle → End
Answer: B – Trigger → Action(s)
Explanation: Every automation follows the IF-THEN logic: IF [trigger happens], THEN [action(s) occur]. The trigger is an event that starts the automation (new email, form submission, file added), and actions are what happens automatically afterward (create task, send notification, save file). You can have one trigger with multiple actions. This trigger-action structure is fundamental to both Zapier and Make, and understanding it helps you think through any automation you want to create.
Question 2
What is the main difference between Zapier and Make?
A) Zapier is for businesses, Make is for personal use
B) Zapier is simpler with a step-by-step wizard; Make offers more power with a visual flowchart interface
C) Zapier is free, Make requires payment
D) Zapier works with more apps than Make
Answer: B – Zapier is simpler with a step-by-step wizard; Make offers more power with a visual flowchart interface
Explanation: Both tools do the same basic thing (connect apps and automate workflows), but they take different approaches. Zapier prioritizes simplicity with a linear, wizard-based interface that’s easier for beginners to learn. Make uses a visual flowchart builder that’s more powerful for complex workflows and offers a more generous free tier (1,000 operations vs. 100 tasks), but has a steeper learning curve. Both have free and paid versions, and both work with thousands of apps. The choice depends on whether you value simplicity (Zapier) or power/pricing (Make).
Question 3
What’s the most important advice when starting with automation?
A) Automate as many things as possible immediately
B) Only use paid plans for reliable automation
C) Start with ONE simple automation, verify it works, then expand gradually
D) Complex automations are better than simple ones
Answer: C – Start with ONE simple automation, verify it works, then expand gradually
Explanation: The biggest mistake beginners make is trying to automate everything at once, leading to overwhelm, broken workflows, and abandoned automations. Instead, identify one genuinely annoying repetitive task, automate it successfully, monitor it for reliability, and only then add more. Simple automations are more reliable than complex ones—they’re easier to troubleshoot and less likely to break when apps update. Building automation skills is incremental: each successful automation teaches you more and builds confidence for the next one. Both free and paid plans can be reliable; the key is starting small and scaling thoughtfully.