n8n connects the tools your business already uses. A workflow starts with an event, applies agreed rules and sends the result to the next system. For a Malaysian SME, that might mean routing an enquiry to a salesperson or matching an order to an inventory record.
Start with one repetitive process whose inputs and exceptions you understand. Agree who owns it, what a successful result looks like and what happens when a step fails. Adding more automation becomes useful once the first workflow is reliable.
What is n8n?
n8n is a workflow automation platform with hosted and self-hosted options. Its source is available under a fair-code licensing model, including the Sustainable Use License. It should not be described as unrestricted open-source software. Check the applicable licence for your intended use, especially if you plan to offer n8n as a service to other organisations. Official n8n licence.
It can connect supported services and APIs into a workflow. Whether a particular integration is practical depends on the source system’s access, permissions, data format and limits. A tool having an API does not guarantee that every action you need is available.
Three workflows worth exploring
These are planning examples, rather than reported client outcomes.
Enquiry routing
Current work: Someone copies an enquiry into a customer record and separately tells a salesperson to follow up.
Possible workflow: Receive the enquiry, check the required fields, look for an existing contact, create or update the record and assign an owner. Route incomplete or ambiguous enquiries for review. Use an acknowledgement that reflects your actual service hours.
Measure: Missed enquiries, duplicate records and time from receipt to assignment.
Order and stock updates
See the stock receipt example for partial deliveries, duplicate events and the checks needed before updating a stock record.
Current work: Staff move order details between a storefront and a stock spreadsheet.
Possible workflow: Receive an order event, validate the order reference, update the agreed inventory system and notify fulfilment. Track cancelled and refunded orders separately. Design duplicate-event checks so a retry does not reduce stock twice.
Measure: Reconciliation differences, failed updates and time spent checking orders.
Document processing with review
Current work: Staff read documents and retype selected fields into an internal system.
Possible workflow: Receive a document, extract draft fields, validate the format and route uncertain results to a person. Only approved data reaches the destination record. Keep the source document and review decision available to the authorised team.
Measure: Correction rate, exceptions requiring review and processing time. Test against representative documents, including poor scans and missing fields, before expanding.
Do you need AI?
Many workflows can use ordinary rules. An approved record moving to another system, a scheduled report or a reminder usually has a predictable trigger and action.
AI may help interpret variable documents, classify enquiries or prepare draft answers. It also introduces uncertain outputs and additional usage costs. Keep people responsible for important approvals and give them a way to correct the result.
Explore ETD’s AI automation service or custom internal systems when the workflow also needs a dedicated interface, permissions or reporting.
Worked example: check an enquiry before routing it
This is a sample-data implementation, not a client case study. It was run in n8n Community Edition 2.43.4 on 14 October 2026 (Malaysia time), with eight checks covering normal input, duplicates, missing or malformed fields, review and a simulated unavailable destination.
Download the sample workflow JSON. In a local test instance, import the file, open Manual start and run the workflow. Verify sample results returns passed: true and testedCases: 8 when all expected routes match. An incorrect result makes that final node fail.
| Input or condition | Expected route | What your team needs |
|---|---|---|
| Valid enquiry with approval | ready_to_route | An agreed destination and owner |
| Same successfully checked event twice | duplicate_suppressed | A stable event identifier |
| Missing ID or malformed email | needs_correction | A correction queue |
Approval missing, false or the text "true" | awaiting_review | A genuine approval decision |
| Destination marked unavailable | retry_pending | A failed-run owner and retry policy |
| That destination marked available on a later sample | ready_to_route | A recovery check before retrying |
The workflow uses Manual Trigger and JavaScript Code nodes. It needs no credentials or AI subscription and performs no external message, API call or CRM write. The approval and availability fields are test inputs; they demonstrate decision points rather than a working approval screen or connection check.
Before connecting real tools: replace test flags with authenticated review and actual destination responses. Store event IDs durably and use atomic writes; this demo only tracks duplicates within one execution. Agree retry limits, alerts, access, retention and reconciliation, then test with representative data. Hosting, connected apps, messaging and any AI usage have separate operating costs.
The official Code node guide explains the runtime. This is an example of why checking the workflow matters as much as installing the tool. Discuss your first workflow.
Cloud or self-hosted?
| Decision | Managed hosting | Self-hosting |
|---|---|---|
| Operations | The provider manages the platform infrastructure | Your team or technical partner manages deployment and maintenance |
| Budget | Check the current plan, execution allowance and required features | Budget infrastructure, backups, monitoring, maintenance and any applicable licence |
| Data flows | Review the provider and every connected service | Review the server location and every connected service |
| Team fit | Useful when you want less infrastructure work | Useful when you have someone responsible for running the system |
Self-hosting gives you control over where the instance runs. It does not guarantee that all data remains in Malaysia or inside your server. A workflow can send information to an external CRM, messaging service or AI provider. Review those destinations, logs, retention and access as part of the design.
Do not select hosting on server price alone. An instance also needs updates, protected credentials, tested backups and a response plan when workflows fail. Check n8n’s deployment options and current plans and pricing before choosing. Plan features and billing terms can change.
What should your project scope include?
Bring a sample of the current process to the discovery session. Useful inputs include:
- The trigger, source documents and destination records.
- Who can view data and who can approve a change.
- Expected volume, operating hours and acceptable delays.
- Exceptions, duplicate events and failed-step handling.
- Required integrations and confirmed API access.
- Hosting, third-party usage, maintenance and support costs.
- Acceptance checks, ownership and handover responsibilities.
ETD’s AI solutions service starts from RM 8,000. That is a starting project price, not a subscription price or a promise that every n8n project fits that budget. The written proposal defines the workflow, integrations, review steps and delivery milestones. Hosting, AI usage and support are scoped separately where applicable. See pricing.
Frequently Asked Questions
Is n8n free?
A self-hosted Community Edition is available, subject to its licence. Infrastructure, maintenance and connected services can still cost money. Paid plans offer different features and allowances. Check the current licence and pricing for your intended deployment.
Will self-hosting keep all our data in Malaysia?
Only the instance’s location is controlled by where you host it. Connected apps and AI providers may process data elsewhere. Map each destination and review access, retention and logging before launch.
Do all workflows need AI?
No. Use rules for predictable steps. Add AI where interpreting variable text or documents is useful, with validation and human review where appropriate.
How long will implementation take?
The schedule depends on integration access, workflow complexity, exceptions and testing. Agree the first workflow and milestones in the proposal instead of assuming that installing n8n completes the project.
How can ETD help?
ETD can scope your workflow, connect the agreed tools, build the automation and plan testing and handover. Start with a free consultation and bring one process you would like to simplify.
