AI automation & no-code
Automate workflows with n8n / Zapier / Make
Triggers, actions, branching, error handling, connecting SaaS tools via APIs and webhooks.
~12 focused hours·beginner
Tools: n8n, Zapier, Make, Webhooks/REST APIs
Market relevance — share of job ads asking for this
What employers mean
You should be able to…
- Build a multi-step workflow with triggers, branching logic and error handling
- Connect SaaS tools via native integrations, REST APIs, or webhooks
- Design retry/exception-handling strategy so a broken step doesn't silently fail the flow
- Choose the right tool (n8n vs Zapier vs Make) for a given use case and budget
- Version and document a workflow so someone else could maintain it
- Test a workflow end to end including failure paths (rate limits, bad input, timeouts)
Learn — free, link-checked
The few resources that matter
Read · beginner · 30 min · zapier.com
Zapier automation guides
Task-specific how-to guides (multi-step zaps, error handling, filters) for patterns beyond the basics course. — Zapier
Use · beginner · 30 min · n8n.io
n8n workflow template library
Hundreds of real, importable workflows (including AI ones) to reverse-engineer instead of starting blank. — n8n
Course · beginner · 60 min · learn.zapier.com
Zapier automation courses
Zapier's own free course library — fastest way to get fluent in triggers/actions on the most-requested tool in JDs. — Zapier
Course · beginner · 90 min · docs.n8n.io
n8n free courses
Official, structured courses on n8n's own docs site — triggers, branching, error handling covered in order. — n8n
Practice
Automated UPI payment-failure follow-up workflow
Build an n8n (or Zapier) workflow that watches for failed UPI transaction webhooks (simulate with a form or scheduled trigger), branches by failure reason (insufficient balance, bank timeout, wrong PIN), and sends a tailored follow-up message via email/WhatsApp API for each branch, with retry logic and a logged error path for unhandled cases.
Done when
- Workflow has at least 3 distinct branches based on failure reason
- Retry logic exists for at least one step that calls an external API
- Unhandled/error cases are logged (to a sheet or database) rather than silently dropped
- Workflow is exported (JSON) and documented with a README explaining each step
Prove it
Evidence a recruiter can check
- Exported workflow JSON in a public repo
- README documenting triggers, branches and error handling
- Screen-recording of the workflow running end to end, including a failure path
Interview
Questions you'll get asked
- Walk me through a multi-step automation you built — what happens when one step fails?
- When would you choose n8n over Zapier for a client, and why?
- How do you handle rate limits or API failures inside an automated workflow?
- How do you document a workflow so a teammate could maintain it after you leave?
- Tell me about the most complex branching logic you've built in a no-code tool.