- n8n builds automated workflows by wiring boxes together on a screen, with AI steps or code where you need them.
- It fits work that moves data between systems that already have an API: LINE OA, Google Sheets, email, a CRM, your accounting program.
- You can install it on your own server or use n8n Cloud. The self-hosted edition carries no license fee for your company's internal work.
- If a system only has a screen, if you need a screen for customers, or if the job is heavy data transformation, another tool fits better.
What n8n is
n8n (say "n-eight-n") is a tool for building automated workflows. You place boxes called nodes on a canvas, draw lines between them, and n8n moves data along those lines every time something happens: a customer messages your LINE OA (LINE Official Account, the business chat channel most Thai companies sell through), or it turns 8 a.m. on Monday. Its developer describes n8n as a fair-code platform for building workflows and AI agents.
It runs in a web browser. People who don't code wire boxes together; people who do can add code. For AI, the AI Agent node connects a language model to tools and lets the model choose which tool to call, and n8n can also connect to MCP servers.
What one workflow is made of
Every workflow starts with a trigger, the first box, which waits for an event: a webhook another system calls, a schedule or a new email. After it come nodes that each do one thing: read a row in a sheet, call a CRM's API, send a message. To open another system, a node needs a credential, a password or token that n8n stores encrypted. Every run is saved as an execution, so you can look back at what each box received and what it passed on.
Draw the work on paper before you open n8n. Teams that skip this step tend to end up with a workflow that runs but that nobody can explain box by box.
The three-column map: event, steps, result
- Column 1, event. What starts the work, in one sentence, such as "a customer sends a name and phone number on LINE OA." If you can't write it, the job isn't ready to automate.
- Column 2, steps. What people do today, one line per step: which system the data comes from, who decides. A line that means reading free-form text is where an AI step goes.
- Column 3, result. Which system the work ends in, and who needs to know when it doesn't finish.
The rule: every line in column 2 must point to a system that has an API or accepts a file. A line that reads "someone opens a screen and clicks" is work n8n can't do for you.
Three workflows a Thai company can use
The first takes in new leads. A customer's message on LINE OA arrives at an n8n webhook. An AI step splits it into fields: name, product of interest, quantity, urgency. n8n adds a row to the Google Sheet the sales team already works in, creates the contact in the CRM and sends a summary to the salesperson for that territory. The LINE node that ships with n8n was built for LINE Notify, which has shut down; reaching LINE OA today goes through the Messaging API with the HTTP Request node.
The second takes in supplier invoices by email, as PDFs or e-Tax Invoices (Thailand's electronic tax invoices). An AI step reads the document number, the supplier's tax ID, the pre-tax amount and the VAT. n8n checks them against the purchase order, sends a matching invoice to a manager to approve, then records it in the accounting program. Some accounting programs have an API, others only take an import file. n8n handles both; you need to know which one you have before you start. Anything tied to money like this should have a human approval step.
The third assembles the weekly report. Every Monday morning n8n pulls sales from the ERP, open tickets from the customer service system and ad spend from the marketing team's sheet into one table, has an AI step write a three-line summary and emails it to management. Whoever used to build the report now only checks the numbers that look wrong. More office examples are in our AI office article, and how to measure the time saved is in the 3 days to 3 hours article.
Self-hosted or n8n Cloud
n8n Cloud is fully managed by the developer. Self-hosted means you install n8n on your company's server or private cloud; n8n recommends Docker Compose with a database for production. In exchange, your team looks after the machine, the backups and the version updates.
The deciding question is whether customer data passes through the workflow. If it does, you have to be able to say where personal data rests under PDPA (Thailand's Personal Data Protection Act). Self-hosting makes that easier to answer, because executions and credentials stay on a machine you control. Back up the key n8n uses to encrypt credentials and keep it somewhere safe; without it, none of the credentials can be decrypted. Sharing credentials between users, storing workflows in Git and single sign-on are in the paid editions.
The n8n license in plain words
The self-hosted Community edition is under the Sustainable Use License. Three points matter. First, you may use and modify it with no license fee for your own internal business purposes or for non-commercial use. Second, you may pay an outside firm to build, install and maintain workflows for you; n8n's license FAQ says so. Third, you may not offer n8n as a service where your customers build their own workflows, and you may not remove n8n's branding and sell it as your own.
If you use n8n inside your company, none of this gets in the way. If you plan to embed n8n in a product you sell, read the full terms or ask n8n first. n8n Cloud has its own terms.
| Situation | n8n | Custom code | RPA | Off-the-shelf automation tool |
|---|---|---|---|---|
| Moving data between systems that have an API | Good fit, the whole flow on one screen | Needs a developer for every change | More than you need | Good fit if the data may leave the company |
| An old program with only a screen | Can't do it directly | Hard | Good fit, a bot clicks for a person | Can't do it |
| A screen customers or staff use every day | Poor fit, simple forms only | Good fit, build an app or website | Poor fit | Poor fit |
| Heavy data transformation, layered calculations | Slow and hard to maintain | Good fit, with tests | Poor fit | Poor fit |
| Customer data must stay in the company | Good fit when self-hosted | Good fit | Good fit when installed in-house | Check where the data rests |
| No developers on the team | n8n Cloud, or hire someone to run it | Needs ongoing support | Needs ongoing support | Fastest to start yourself |
When to use something other than n8n
The first sign: the system you need to touch only has a screen, with no API and no file import, such as an old program on a staff PC. That job belongs to RPA, where a bot clicks for a person. The second: what you need is a screen people open every day, such as a booking system or a dealer portal. That is an app, with n8n doing work behind it.
The third: the job is transforming a lot of data, such as reconciling a month of bank transactions, calculating multi-tier commissions or migrating data out of an old system. Code with tests is easier to maintain than a workflow with dozens of boxes. More in connecting a new app to your ERP, accounting and legacy data.
Hypothetical case
A cleaning-supplies distributor in Nonthaburi (name and details invented) asks its IT staffer to try a first workflow in n8n: leads from the website form and LINE OA go into Google Sheets, and the sales team gets a message.
In week three, a sales assistant renames the column "Phone" to "Contact number." The workflow keeps running without errors, but the phone numbers of new leads are missing for the whole week. In month two, the IT staffer leaves and the company closes his Google account. The credential tied to that account stops working at once, the whole workflow stops, and nobody knows where to look. Second time round, the company moves the credential to a company account, adds an error workflow that posts to the IT team's LINE group, adds a step that checks every row has a phone number, and writes one page on which columns the workflow reads.
What to ask before adopting n8n
These work whether your own team starts or you hire someone. If you're not yet sure which job pays off, start with calculating the cost of manual work.
- Does every system in the steps column have an API or accept a file?
- Does customer data pass through the workflow? If so, self-hosted or n8n Cloud?
- Are credentials tied to a company account or a personal one, and who holds the encryption key?
- When a workflow fails, who is told, and through which channel?
- Which steps touch money or customers, and who approves them?
- Who can edit workflows, and how do you roll back to the previous version?
- If n8n will sit inside a product you sell, does that use fit the Sustainable Use License?
For the development team · Error workflows, retries, idempotency, secrets and version control
Set an error workflow in Workflow Settings for every production workflow. It starts with an Error Trigger, which receives the execution ID, the error message and the last node that ran; forward that to LINE or email. Turn on Retry On Fail only for nodes that call external systems. Any step that writes data needs an idempotency key, such as the invoice number, so a retry never records the same item twice. Set N8N_ENCRYPTION_KEY yourself and keep it in the company's secret management. n8n stores workflows as JSON; if your edition has no source control, export them to Git yourself. Exported files carry credential names and IDs, not secret values, except headers in HTTP Request nodes imported from cURL. Set the timezone to Asia/Bangkok, because the instance default is New York time. Community nodes have full access to the machine n8n runs on; use only ones you have reviewed.
How we build and hand over n8n workflows
DNA Maker starts by watching the work your team repeats every day, draws the three-column map with you, and picks the first workflow that gives your team time back fastest. We install n8n on your company's server or cloud account, so the credentials and the encryption key stay in your hands, and connect LINE OA through the Messaging API, Google Sheets, email, your CRM and your accounting program. Steps that touch money or customers have a human approval point, and every workflow has an error workflow that alerts someone when it fails.
The people who work with you are DNA Maker's own team; we don't subcontract. At handover you get every workflow file, documentation node by node, and training so your team can change messages or approvers without us. Most first sets of workflows take two to six weeks. If your job should be an app, RPA or code, we'll say so on day one. Details are on the n8n automation and AI workflow pages, or ask Dream in the chat.
SOFTWARE ENGINEERING GLOSSARY
Software engineering glossary
| Term | What it is | A simple example | What executives should ask the development team |
|---|---|---|---|
| Workflow | A sequence of steps a system runs on its own when an event happens | A customer messages on LINE and the name lands in the sheet and the CRM | What starts this workflow, and which system does it end in? |
| Webhook | An address one system sends data to the moment something happens | LINE sends a customer's message to n8n as soon as it's typed | If someone learns this address, can they send fake data in? |
| Human approval | A point where the workflow stops and waits for a person to decide | A manager approves an invoice before it's recorded | Which steps need approval, and is who approved recorded? |
| Idempotency | Running something again without doubling the result | The same invoice arrives twice and is recorded once | If the workflow runs twice, does the item go in twice? |
| Secret management | Keeping passwords and keys somewhere safe, apart from the work itself | n8n's encryption key sits in the company's secrets vault | If the person who set this up leaves, can we still reach the key? |
n8n, Sustainable Use License
n8n Docs, License FAQ
n8n Docs, Choose how to use n8n
n8n Docs, Hosting
n8n Docs, Deployment environment variables
n8n Docs, Credential sharing
n8n Docs, Source control and environments
n8n Docs, AI Agent node
n8n Docs, Advanced AI
n8n Docs, Nodes
n8n Docs, Error handling
n8n Docs, Workflow settings
n8n Docs, Executions
n8n Docs, Export and import workflows
n8n Docs, Community node risks
n8n Docs, Line node