Educational resource · no-code & low-code
What do you do when your team needs a simple approval tool but the IT backlog stretches into next quarter? Nufego is a Czech-focused knowledge base that walks non-technical professionals through Airtable, Notion, and Make.com, one screenshot at a time. No software is sold here, only explanations.
Written for office coordinators, HR generalists, operations leads and finance assistants who are asked to "just build something" in a spreadsheet-adjacent tool. Every walkthrough is based on the free or entry-level tier of the tool being discussed.
Plenty of Czech companies run on a mix of email chains, shared spreadsheets and someone's memory of "how we do it." IT departments are usually small, already busy with security and infrastructure, and rarely have room for a two-day request to build an internal leave-approval form. No-code and low-code tools fill that gap, but only if the person building the tool understands what the tool is actually doing.
Nufego does not sell Airtable, Notion or Make.com. It explains them. Each guide includes screenshots taken from real configurations, described step by step, so a marketing coordinator or an office manager can follow along without a developer sitting next to them.
Core topics
Every internal request is a little different. A weekly approval chain is not the same problem as a shared client register, and a shared client register is not the same problem as connecting two subscriptions together. The cards below map common Czech-office situations to the tool that tends to fit.
Airtable
Can a table with a status column really replace an approval email chain? Usually, yes, for anything with a handful of steps. This walkthrough covers setting up a "Submitted → In review → Approved / Rejected" status field, a linked table for approvers, a view filtered to "waiting on me," and a basic automation that notifies the next person when a status changes.
Read the walkthrough
Notion
A Notion database with a few relation fields and filtered views can absorb what used to require a small custom app: an equipment register, an onboarding checklist, a simple content calendar. This guide walks through where that substitution holds up, and where it starts creaking under multi-user editing or complex permissions.
See related reads
Make.com
Make.com works with modules and connections instead of functions and syntax. This walkthrough explains triggers, actions, filters and error handlers using a plain example: sending a Google Sheet row into a shared calendar whenever a form is submitted.
Read the walkthroughRow limits, automation caps, and fragile multi-step logic. Some situations genuinely call for a developer.
Explore the boundaryWho can see what, and who can edit what, once a spreadsheet turns into a shared internal system.
Read the notesPractical walkthroughs
Each guide follows the same shape: a real situation, a screenshot of the relevant screen, a short explanation of what each field or module does, and a note on what could go wrong. No abstract theory before showing the actual interface.
From a blank base to a working request form in roughly the order a first-time builder would actually take it, including the mistakes that are easy to make with linked records.
What to check in the module list, the data mapping, and the error handler before switching a scenario from "off" to "scheduled."
Knowing your limits
Is it possible to build too much on top of a spreadsheet-style tool? It happens more often than expected. A Notion database with fifteen relation fields and three formula chains can become difficult for anyone but its original author to maintain. An Airtable automation calling four external webhooks in sequence introduces failure points that are hard to debug without reading logs.
Some signals tend to appear before a no-code setup becomes a liability rather than a convenience:
None of this means no-code tools are a stopgap to be replaced eventually. Many internal tools stay in Airtable or Notion for years without issue. The point is recognising, early, which category a given project falls into.
Common questions
No. Every walkthrough on Nufego assumes no programming background. Where a formula or expression is needed, it is explained in plain terms alongside the screenshot showing exactly where to type it.
No software is sold or resold through this site. Nufego is an independent educational resource. Any subscriptions or accounts you use with these tools are set up directly with the tool's own provider.
The examples reflect situations common in Czech office environments, such as approval chains involving a manager and finance, or internal registers kept in Excel before being migrated. The underlying tool mechanics apply more broadly.
Interfaces change. When that happens, the affected guide is flagged and a note is added to the Corrections and Updates page describing what changed and when.
Content is prepared by people who build and maintain internal no-code tools in ordinary Czech business settings, then reviewed for clarity before publishing.
If a particular Airtable base, Notion setup or Make.com scenario isn't behaving the way you expect, you can describe the situation and we'll point you toward the relevant walkthrough or explain what's happening.
Get in touch