All capabilities · AI automation & no-code

Add LLM steps to business automations

Classify emails, extract fields from documents, draft replies inside n8n/Zapier/Power Automate flows.

~10 focused hoursbeginner
Explore 5 tools for this project
Market relevance

Which roles ask for this — and how often

Share of job postings in India, per role, that name this capability.

What employers mean

You should be able to…

  1. Classify inbound emails or tickets using an LLM step inside a workflow
  2. Extract structured fields from unstructured documents (invoices, forms) inside an automation
  3. Draft a reply or summary using an LLM step, with a human-approval gate before sending
  4. Prompt-engineer an LLM step to return reliable structured output (JSON) an automation can parse
  5. Control cost by choosing the right model size/provider per automation step
  6. Handle LLM step failures (bad JSON, timeout) without breaking the whole flow

Needs first: Automate workflows with n8n / Zapier / Make, Design and version prompts systematically

Learn — free, link-checked

The few resources that matter

Tools for practice

Choose a tool for the job

Start with one tool for each part of your project. You don’t need to learn them all.

Go to the practice brief

5 tools to explore

OpenAI API

Build · Test

Connect model calls, tool use and structured responses to your own application.

Claude API

Build · Test

Build model-backed features with messages, tool use and responses you can evaluate.

Power Automate

Automate

Automate a repeatable business process using cloud flows or desktop actions.

Practice

AI triage automation for Hindi and English support tickets

Build a workflow (n8n or Zapier) that takes a support message in Hindi or English, uses an LLM step to classify category and urgency and pull key fields into structured JSON, drafts a suggested reply, and routes high-urgency tickets to a human-approval step before anything is sent. Feed it real bilingual text from the MASSIVE dataset, which already carries intent labels, so you can check what the LLM step got wrong instead of guessing.

Start from

MASSIVE (AmazonScience) hi-IN and en-US utterances as your ticket text — real user requests in both languages, already intent-labelled so you can grade the LLM step

Milestones
  1. Get the workflow running end to end with a hardcoded LLM response · ~1.5h
  2. Write the classification prompt until it returns parseable JSON on 10 varied tickets · ~2.5h
  3. Add the malformed-output catch and the error log · ~1.5h
  4. Add the urgency branch and the human-approval gate before any send · ~2.5h
Done when
  • LLM step reliably returns valid structured JSON (test with at least 10 varied ticket examples)
  • Workflow handles both Hindi and English input correctly
  • High-urgency tickets are routed to a human-approval step, not auto-sent
  • Malformed LLM output is caught and logged rather than crashing the workflow
Prove it

Evidence a recruiter can check

  • Ten input/output pairs across Hindi and English showing exactly what the LLM step returned, including at least one it got wrong
  • The exported workflow with the JSON-parse failure path visible as its own branch in the node graph
  • A recording of a high-urgency ticket stopping at the human-approval gate instead of auto-sending
  • The prompt itself, with the output schema and the retry you added to stop malformed responses
Signal it

Added an LLM triage step to a support automation — classifies Hindi and English tickets into structured JSON, catches malformed output instead of crashing the flow, and holds high-urgency replies for human approval.

Interview

Questions you'll get asked

  1. How would you add an LLM step to classify incoming support emails inside n8n or Zapier?
  2. How do you get an LLM to reliably return structured JSON an automation can parse?
  3. What happens in your workflow when the LLM step returns malformed output?
  4. How do you decide between a cheap/fast model and a more capable one for a given automation step?
  5. Tell me about a workflow where you added a human-approval gate before an AI-drafted action executed.