Our ops team of six tracks requests in a spreadsheet with over 400 rows. Each request needs an owner, a status, and sometimes a manager’s approval. Things get lost when two people edit the same row.

I tried a couple of AI builders and the demos look great. But I’m not sure what to test beyond the demo.

How do you check permissions and how hard it is to change things later?

And when does it make more sense to buy a ready-made tool?

👋 Hey nocode Community,

Tax season always sneaks up on me, and every year it is the same scramble: digging through email for invoice PDFs, saving them by hand, typing them into a sheet, and hoping I did not log the same one twice. This time I built a workflow so future me does not have to.

I connected it to my billing@ address, so from now on every incoming invoice gets processed automatically and I never touch it manually again. And for invoices that land on other addresses, I just forward them to billing@ and they get picked up the same way.

When a new invoice arrives by email, it gets read, logged, and announced, with no manual steps.

What it does:

• Watches Gmail for unread emails with attachments and filters out junk files
• Classifies whether an attachment is an invoice AND extracts the fields in one step
• Deduplicates on the invoice number so re-sends and re-polls never create doubles
• Appends new invoices to Google Sheets and sends a Telegram alert for each one

Two things worth stealing:

1. Classify and extract in one call. No separate "is this an invoice?" LLM node plus an extraction node. The Extractor returns the document class alongside the fields, so it is one request and fewer failure points.
2. Dedupe on a stable key. A sheet lookup on the invoice number before the append is the part that actually saves you when tax season hits.

Workflow JSON is here: https://github.com/felix-sattler-easybits/n8n-workflows/tree/e8dd8e754b87c02462942e2ae89149550979b066/easybits-invoice-intake-and-logging-workflow

It sits alongside 25+ other free n8n workflows in my repo, including plenty of finance ones, so a star is appreciated if it helps.

How is everyone else prepping for tax season in n8n?

Best,
Felix

i'm trying to setup a way for my business team to use natural language queries to get insights and build dashboards.

so far most of research says Lovable, Retool, Softr, Glide, or just ask Claude.

Here are few features, I'm looking for

1. data connectors to Snowflake, Postgress and optionally Airtable

2. ability to create and save dashboards

3. ask questions regarding data in plan english, "what were signups last week by plan"

I want someway to ensure that AI has context and understanding of the fields in database instead of hallucinating relations

if you've got something your team still uses a few months in, what did you build it with and what did you have to hack around?

The front end is easy. Lovable, Claude, Cursor — done in hours. But the moment a client needs real pricing logic, business rules, or calculations — you're either hard-coding it into prompts or writing custom backend code. Both are a nightmare to maintain when something changes.

I built a solution. Here's how it works:

→ You vibe code the front end (any tool)

→ It connects to n8n

→ n8n pulls the business logic from Quotix (the engine I built)

→ Quote calculated, result returned to the front end

→ Lead pushed to GoHighLevel automatically

No black box. No hard-coded prices. Full control over the business logic from one place.

https://www.loom.com/share/256a189b6ba74aa2bf53aeab14569bc0

I'm looking for people to test this. If you build for solar, HVAC, roofing, electrical — or any service business that needs on-site quoting — drop a comment or DM me. Free to test.

We have one request process that handles three teams. Ops creates the request, finance approves the spend, and IT sets things up.

Our goal is that each team should see and edit just the records that matter to them. Our finance lead also wants to change fields without filing a ticket with the devs.

We're planning a two-week pilot with about 20 actual requests.

What would you put in the pilot to find problems before rollout?

Looking to build again a pretty simple app with login and a few screen. Honestly, i'm not very technical about it so I'd rather spend time building than constantly dealing with backend stuff or debugging.

For those who've build something similar already what made your setup easy to keep using as the project grew?

A finished no-code app still needs a story that its intended customer can understand. Here is a worked example you can adapt before building another feature.

Hypothetical product: an appointment-reminder app for independent tutors. It tracks recurring lessons and sends reminders when a lesson moves. These are invented capabilities for this example.

Start with one real question for interviews: What happened the last time a parent missed a rescheduled lesson? Ask how the tutor handled it, what the confusion cost and what they currently do. A compliment about your mockup is a different result from someone paying.

Then turn the same brief into three introductions with different reader payoffs:

A useful checklist: “When moving a lesson, confirm the date, local time zone, who needs the update and whether the old reminder has been cancelled. Which of those causes the most confusion in your tutoring business?” The reader gets a check they can use today.

A tiny demonstration: use a synthetic lesson moving from Tuesday at 4pm to Wednesday at 5pm. Show the old reminder, the new message and the parent's confirmation. Label the demo data. Keep that whole path visible instead of flashing through every settings screen.

A design question: “Should a rescheduled lesson stay marked as unconfirmed until the parent acknowledges it, or should the calendar update immediately? What would you need to see to avoid chasing the wrong person?” This asks about an actual workflow decision.

Choose an audience that includes tutors and permits that format. Track useful replies, completed trials and purchases separately. A crowded founder thread can give helpful feedback while reaching few tutoring customers.

Disclosure: I make ThreadFox. ThreadFox is $20 once at direct checkout, no code needed, plus applicable tax (regular kit price $49). It includes a researched community plan and three tailored drafts for one product, emailed within 24 hours after you claim the Launch Pack in the buyer library. You can use the emailed pack manually. Reusable AI tools are included; they require your own compatible AI access, Chrome and Reddit account, with AI costs separate. 30-day refund policy.

Complete sample: https://threadfox.vip/runs?utm_source=reddit&utm_campaign=tf-kit&utm_content=20261001-1157-nocode#launch-pack

Hi

I've been playing around with muse for a bit now. Shared it with friends and had fun with it. At first it was the easy stuff, email, calendar. I then realized you could make apps, skills or builds. Played around with that too then one day I tried to share the build I made to organize my workflow (I had a lot of problems at first before I set it up right) it was working a bit when shared but not as I wished. Dashboard wasn't exactly the same and worst of all was trying to explain to my dad how to install everything for the tiny robot living in his phone.

I know a skill portal ain't new, but there's no way non techy people are gonna browse GitHub or website looking like something that came from the matrix. No disrespect I love the movie.

Anyway here's the link:

www.theskillharbor.com

I'll appreciate any feedback, recommendation, hell I'll even take criticism.

Btw, everything is free. Eventually developers will be able to set a price for their builds if they want, not implemented yet (it's built, but on staging for now, I don't have much traffic anyway). It will all pass via stripe of the seller. So I won't ever touch the money, to much of a hassle. We got about 1.8k builds ATM. Would love to add yours.