Skip to content
estudIA

Tutorials3 min read

Automate Tasks with AI Using n8n, Make or Zapier

Build your first AI automation without code: pick the right task, choose between n8n, Make and Zapier, add an AI step, test it and keep a human in the loop.

In short

  1. Pick a repetitive task. Choose a frequent, rule-like task with clear inputs and outputs, such as sorting incoming emails.
  2. Map trigger, steps and output. Write down what starts the workflow, each step in between and where the result must end up.
  3. Choose a tool. Pick Zapier for the fastest start, Make for visual multi-step scenarios or n8n for control and self-hosting.
  4. Add the AI step. Insert an AI step with a precise prompt and ask for a structured output such as a category and a short summary.
  5. Test with real data. Run the workflow on a sample of real cases, including unusual ones, and fix the prompt where it fails.
  6. Keep a human in the loop. Send drafts or flagged cases for review before anything is sent to customers or changes important data.
  7. Monitor and maintain. Watch errors, AI costs and usage limits, and review results regularly.

Automation tools connect your apps — email, forms, spreadsheets, CRM, chat — so that when something happens in one, actions happen in others. Adding an AI step lets those workflows handle tasks that used to need a person to read and decide: classifying messages, extracting data from documents, drafting replies or summarising.

This tutorial walks you through building a first automation with an AI step, using the example of sorting incoming support emails. The same method works for any similar task.

1. Pick the right task

Good first candidates are:

  • frequent (daily or weekly), so the effort pays off;
  • rule-like, with a clear input and a clear expected output;
  • low risk if one case goes wrong, at least at the start.

Sorting emails, extracting fields from invoices into a spreadsheet, tagging form responses, or summarising meeting notes into your task manager all fit. Avoid starting with anything that sends money, deletes data or answers customers without review.

2. Map the workflow on paper

Before opening any tool, write three things:

  • Trigger: what starts it? A new email arrives in support@.
  • Steps: what happens in between? AI reads the email and returns a category, urgency and one-line summary.
  • Output: where does the result go? A new row in a spreadsheet, and urgent ones also posted to the team chat.

This map is the specification. If you cannot write it down, the automation will not work either.

3. Choose a tool

Feature Zapier Make n8n
Best for Fastest start, simple workflows Visual multi-step scenarios Control, complex logic, self-hosting
Learning curve Lowest Medium Medium–high
Free option Limited monthly tasks Limited monthly credits Free self-hosted Community Edition
AI Built-in AI steps and agents Built-in AI modules and agents AI agent and model nodes, many providers

Current prices and limits are in our model and tools comparison. If you will handle personal data and want it to stay on your own server, n8n’s self-hosted option is the one that allows it.

4. Add the AI step

In your tool, add an AI step after the trigger and connect your AI provider (with an API key or the tool’s built-in AI credits). Then write a precise prompt and ask for structured output, so the next steps can use the result reliably:

You classify support emails for an online shop.

Return JSON with exactly these fields:
- category: one of "billing", "delivery", "returns", "technical", "other"
- urgent: true if the customer mentions a deadline, legal action or a payment
  error; otherwise false
- summary: one sentence, maximum 20 words

Email:
{{email body}}

The double braces stand for the field your tool inserts from the trigger. A small, fast model is usually enough for classification and keeps costs low.

5. Test with real data

Run the workflow on 20–30 real past emails, including messy ones: replies with long quoted threads, emails in another language, emails with two problems. Compare the AI’s categories with what a person would choose. Where it fails, improve the prompt — add a definition, an example of a borderline case or a rule — and test again.

6. Keep a human in the loop

For anything customer-facing, start with the AI drafting and a person approving. For example, instead of sending replies automatically, save drafts in your email or post them to a channel for review. Once results have been reliable for a while, you can decide which low-risk cases to fully automate.

7. Monitor and maintain

Automations break quietly. Turn on error notifications, check AI usage and costs each month, and review a sample of results regularly. When your categories, products or policies change, update the prompt.

Going further: AI agents in automations

All three tools now offer AI agents: steps where the model decides which of several tools to use — look up an order, check stock, search your help centre — before producing a result. They are powerful but less predictable than a fixed workflow. Start with fixed steps, and move to an agent only when the task genuinely needs flexible decisions. Our guide to what an AI agent is explains the trade-offs.

Frequently asked questions

Do I need to know how to code?

No. All three tools are visual. Basic logic (if this, then that) and a clear understanding of the task are enough to start; code steps are optional.

How much does an AI automation cost to run?

You pay the automation tool’s plan plus the AI usage. For short texts like emails, the AI cost per run is usually a fraction of a cent with a small model, but it adds up at volume — check your provider’s prices.

Is it safe to send customer data through these tools?

Only with appropriate agreements and settings. Under the GDPR the automation and AI providers act as your processors, so review their data processing terms and send only the data the task needs.

Glossary terms

Sources

Related articles