Practice Task

Practice: Compare three given automation options

Compare Zapier, Make, and a custom Node.js script for a small-business automation.

Back to practice tasksEnter task room
Practice typeRealistic client scenario · no cash reward
SubmissionsOpen practice; every contributor can submit their own version
Review outcomePass: +25 Trust Points. Revision or not passed: no points until fixed.
Current statusOpen
Practice boundaryRead the exercise here; submit and revise in the task room

The brief is not the submission area

This page gives the customer scenario, source material, deliverables, review criteria, and suggested format. Formal practice submissions, files, revision notes, and review outcomes belong in the task room so each attempt is auditable.

Exercise brief

Use this page to understand the scenario, assumptions, source material, deliverables, and pass/fail criteria before working.

Task room

Submit the completed result, upload supporting files, send clarification messages, and resubmit a new version if revision is requested.

Reusable practice

There is no participant quota. Multiple contributors can submit, and each version is reviewed against the same criteria.

Review record

Outcomes are pass, revision needed, or not passed. Only a passing version earns Trust Points or case-review eligibility.

Client Scenario

What problem are you solving?

A small business has no dedicated engineer. Web form submissions should be written to Google Sheets, a Feishu group should be notified, and a weekly summary should be generated.

System Context

Use these assumptions

The candidate options are fixed: A) Zapier, B) Make, C) custom Node.js script. You do not need to build the automation; produce a client-readable comparison and recommendation.

Source Material

Base your work only on this material

Workflow: form submission -> Google Sheets row -> Feishu group notification -> weekly summary. Client cares about cost, stability, maintenance difficulty, launch speed, and whether failures are visible.
Deliverables

What to submit

  • A/B/C comparison table
  • Recommendation order
  • Best-fit conditions for each option
  • Failure risks and monitoring suggestions
  • Questions to confirm with the client
Review Criteria

What makes a result pass review

  • Compare all three supplied options
  • Give recommendation order and reasons
  • Do not answer only 'it depends'
  • Consider small-business maintenance capacity
  • Explain tradeoffs in client-readable language
Submission Format

Recommended format

  • One-paragraph conclusion
  • Comparison table
  • Risk and confirmation-question sections