Salut ! ça fait 6 ans que mon frère développe luna-park.app (en deux mots c'est un éditeur avancé de nocode, pas du tout IA first, tu peux tout construire à la main et éventuellement utiliser ton IA si t'as envie)

Je l'ai rejoint il y a presque 2 ans parce que je trouvais ça incroyable. Je suis ingénieur comme lui et je m'occupe de la com / faire des tutos / faire des retours produits, bref profil un peu couteau suisse.

Récemment on a eu pas mal d'opportunités avec les écoles d'ingénieurs et on se projette sur l'éducation : les étudiants adorent, on garde le principe de la programmation mais sans la syntaxe, et ça évite qu'on leur donne un sujet qu'ils copient collent sur chatgpt

MAIS : on galère un peu à atteindre notre cible de base qui sont les nocodeurs avancés et développeurs; on sait que c'est ultra difficile de convaincre des gens de s'investir un peu dans un outil surtout avec tous les builders IA first.

J'avais fait un post l'année derniere sur r/nocode (lien ici) qui a confirmé l'intérêt des gens pour la promesses (1000 inscrit en 2 jours) mais presqu'aucun ne s'est donné la peine d'essayer de créer un vrai projet, d'aller au bout de nos tutos. Donc on a très probablement un problème d'onboarding qu'on essaye de résoudre, mais peut être autre chose qu'on ne voit pas ?

Je suis preneur de feedback brutal ! ;)

I've spent the last few months building something and I'm finally at the point where I want to share it properly rather than just quietly hoping people find it.

The idea came from a frustration I kept seeing (and feeling myself): SQL tutorials teach the syntax fine but there's never a reason to care about the answer. You filter a table called employees, get a result, and nothing happens. Your brain doesn't bother keeping it.

I wanted to try a different approach. QueryCase teaches SQL through detective investigations. You get a briefing from Chief Fox (our mascot), a real database to query, and a mystery to crack. The JOIN matters when a suspect has an alibi. The WHERE clause matters when you're trying to find who entered the building at 22:13. The SQL is the tool for solving something, not the point in itself.

Here's what's actually in it:

• A structured learning path across 54 cases, going from Recruit through Rookie, Detective, Senior Detective, and Chief Detective. Each rank has drills and a level exam to pass before you progress.
• Sandbox mode where you can explore real datasets (IMDB movies, Spotify, sports stats, Steam games) and run whatever you want with no pressure and no mystery attached. Just free exploration against actual data.
• Everything runs in the browser using DuckDB WASM so there's nothing to install.

I'm a solo developer and this is genuinely early days. I'm sharing here because this community is exactly the kind of people I built it for, and I'd rather get honest feedback now than find out later I've built the wrong thing.

What's missing? What would make you actually stick with something like this versus what you've used before?

querycase.com if you want to take a look.

Any feedback appreciated!

Hey everyone,

I built SaaSBoard (https://saasboard.app/), a visual directory for SaaS startups, where founders can showcase their products on an interactive grid.

If you're currently building a website or app and looking for extra reach or backlinks, feel free to check it out and claim your spot on the grid.

Would love to hear any thoughts, feedback, or suggestions from the community!

👋 Hey n8n Community,

A while back I built a purchase order extractor for a friend who was drowning in PO PDFs. It let him batch-upload the documents through a form and pull all the data into a Google Sheet through the easybits extractor. That alone saved him a lot of manual re-typing.

Last week he told me his company is moving onto SAP, and he asked whether the workflow could also spit out EDI files so he can push the orders straight into the ERP instead of keying them in by hand. So I built that in, and while I was at it I made the whole thing a good bit more robust.

How it's set up:

• Batch PDF upload: the form takes one or many PO PDFs at once, and a toggle lets you decide per submission whether you also want EDI files out.
• Extraction: each PO runs through the easybits extractor one at a time and lands in a Google Sheet, one row per line item, with the source document name on every row so you can always trace a row back to its PDF.
• EDI 850 generation (optional): when the toggle is on, each PO is also turned into a valid X12 850 EDI file and saved to a Drive folder, ready to upload into SAP. A separate sub-workflow handles the generation, so the main flow stays clean.
• Duplicate check: after extraction it checks the PO number against what's already in the sheet. If that PO was processed before, it skips it, so you never get double entries.
• Flag summary: the completion screen tells you if any field was missing or looked off in an extraction, and lists any duplicates it skipped along with the PO number.

Short video attached showing a batch run of three POs with EDI generation switched on, then a re-upload of one of them so you can see the duplicate check catch it and report which document and PO number it was.

Both workflows (the main one plus the EDI sub-workflow) and a setup guide are here: https://github.com/felix-sattler-easybits/n8n-workflows/tree/f4dec1bef3561aa9e803bb21b96ebff1ab0dde04/easybits-purchase-order-extractor-v2

You'll also find it alongside 20+ other n8n workflows in my repo. If it's useful to you, a ⭐ really helps other builders discover it too: https://github.com/felix-sattler-easybits/n8n-workflows

Curious how the rest of you are handling the PO-to-ERP step. Are you going through EDI, hitting a direct API, or still uploading into the ERP by hand?

Best,
Felix

Please help! My app is being used a ton all of a sudden and my integration credits are about to max out. I have maybe 24-48 hours until my app stops working. The problem is that I'm not making enough MRR to justify buying the elite subscription at $160/month, and I've already paid for a full year of the pro subscription. What can I do to prevent the app from stopping? I have a lot of users and this issue arose suddenly. Do I have other options besides upgrading, like buying more credits for this month?

I changed the model that the app uses to SIGNIFICANTLY reduce the integration credit usage next month... So ideally I don't need the elite credit count, except for the remaining 2 weeks until credits reset. Advice??

👋 Hey n8n Community,

I've built a lot of finance workflows over the last few months for friends who run small businesses, and going back through my library I realised I'd never shared the most basic one people keep asking for: a simple batch invoice extractor. So I cleaned one up and pushed it to the n8n template library: Extract batch invoice data from form uploads with easybits and Google Sheets.

The idea is simple. You upload one or many invoices (JPG, PNG, or PDF) through a single form, and it extracts the data from all of them in one go, instead of dragging every invoice in one by one. Each invoice lands as a row in a Google Sheet, and when the batch finishes, the form shows a summary marking every file with a ✅ or ❌ so you instantly see which ones need a second look.

How it's set up:

• An n8n Form takes one or more invoice files.
• The files get split into one item per file, keeping the original filename.
• It loops over the invoices one at a time, sending each to the easybits Extractor, which returns the fields (invoice number, date, vendor, total, and so on) as a structured data object.
• The filename gets reattached, and a check runs over the critical fields.
• One row per invoice is appended to Google Sheets, with a pass/fail status.
• A batch summary is shown as the form's completion message.

A few things from the build that might save you time on your own flows:

• The extractor bundles everything you hand it into one request. Pass it all the files at once and you get one merged result back, not one per invoice. Looping one file at a time is what gives you a clean result per invoice. This one cost me a debugging session.
• Treat "missing" as a signal, not an error. The extractor returns null when a field isn't on the document. Instead of fighting that, I lean into it: a small check flags any invoice missing a critical field, which is what powers the ✅/❌ summary. Worth catching the sneaky empties too (the string "null", empty strings, whitespace), so nothing slips through looking present when it isn't.
• The fields are yours to change. The mapped fields are just a starting point, so you can add whatever you need to pull from your own invoices, like a VAT ID, PO number, or IBAN. The extractor also has auto-mapping, so you can upload one example invoice, let it detect the fields, and tweak from there.

I also recorded a short video showing how it runs end to end, which I'll post alongside this.

For more free workflows, feel free to check my GitHub as well: https://github.com/felix-sattler-easybits/n8n-workflows. A star helps other builders find it, so I'd be really thankful for that support.

How do you all handle the invoices that fail extraction? Curious whether people flag them for manual review like this or route them elsewhere.

Have a good start to the week.

Best,
Felix

We just updated our No-Code Landscape for 2026.

The no-code ecosystem has changed a lot since we first created it, so this year we mapped 100+ no-code tools across 10 categories, including:

• Database Builders
• Internal Tools
• Website Builders
• Mobile App Builders
• Productivity
• Automation & Integrations
• AI-Native Builders
• AI Agents & Intelligent Automation
• App Builders
• Forms

The biggest change this year? AI has become a much bigger part of the landscape. We added dedicated categories for AI-native builders and AI agents because tools like these are changing how people build software.

We also looked at things like open source, self-hosting, free plans, and built-in AI to make it easier to compare tools.

👉 Download the 2026 landscape image

We also turned the list into an interactive directory where you can explore all 100+ tools by category and compare their features:

👉 Browse the interactive directory

👉 Read the full guide

What would you add or change?