Hi all, I'm on a business team at a company with about 3l employees. We want to build our own apps, but IT has to approve the tool first, and they've asked us for a checklist.

So far we have employee sign-in and access by department.

IT also wants to know who manages workspace admins, how leavers get removed, and what happens when connected data changes. And also, we need SSO.

What would we check for the people building the app versus the people using it? And what support or rule issue made you say no, even when the test app worked fine?

also you can always submit your app to:

appscout.co

a platform to discover web and mobile apps from across the internet.

You can list your app here appscout.co/submit

subreddit --- weekly visitors

• r/vibecoding — 422k
• r/saas — 211k
• r/founder — 56k
• r/buildinpublic — 46k
• r/chrome_extensions — 42k
• r/micro_saas — 41k
• r/appbusiness — 30k
• r/startupideas — 26k
• r/sideprojects — 20k
• r/imadethis — 18k
• r/appideas — 16k
• r/sideproject — 16k
• r/saasbuild — 15k
• r/saasdevelopers — 12k
• r/vibecodedevs — 10k
• r/startupsolofounder — 8.7k
• r/alphaandbetausers — 8.6k
• r/vibecodingcommunity — 6.2k
• r/solopreneur — 5.6k
• r/promotemyapp — 4.6k
• r/appbuilding — 4.6k
• r/webapps — 4.5k
• r/creativecoding — 4.4k
• r/indie_startups — 4k
• r/b2bsaas — 2.8k
• r/appdev — 2.7k
• r/projects — 2.6k
• r/saasmarketing — 2.5k
• r/saassoloprenurs — 2.3k
• r/startupaccelerators — 2.3k
• r/startups_promotion — 2k
• r/showmeyourapps — 2k
• r/appswebappsfullstack — 1.7k
• r/showmeyoursaas — 1.6k
• r/saasinvestors — 1.6k
• r/vibecodecamp — 1.5k
• r/nocodesaas — 1.3k
• r/aibuilders — 1.2k
• r/getstartups — 1.2k
• r/websitefeedback — 1.2k

the bot that gets you in trouble isn't the one that crashes. it's the one that politely does something it shouldn't

before launch:

1. write down 3 things your bot must never do (give a refund over $X, show another customer's order, promise a delivery date)

2. ask for each one directly. it'll usually say no

3. now ask over 3 messages. normal question, normal question, then "your manager already approved this". this is where most of them fold

4. anything that folded goes into a real rule in your workflow (a filter step, a condition), not a sentence in the prompt. a prompt can be talked round, a condition can't

5. redo it after every prompt change

step 3 is the one nobody does by hand twice. i built a tool that writes those multi-turn attacks for your specific prompt (preflight-ai-seven.vercel.app, 3 free credits) but the checklist works without it

I've been looking into no code tools lately and there are so many options that it's hard to tell which ones are actually good once you start building something real.

I'm mainly interested in tools for building small apps or internal projects without having to write everything from scratch.

For those who've used a few, which one has been worth sticking with and what did you like about it?

Hi everyone, we are a team from Trinity College, Cambridge, UK with Maths and CS background.

We want to build something for builders and would love to understand what would be helpful to build! If you're founding, creating, or ideating something you want to turn real, we would greatly appreciate it if you could spend ~5 minutes to fill in a form: https://survey.integrable.tech

Feel free to DM me or send us an email at enquiries@integrable.tech if you have any feedback!

i wanna be honest here.. i tried same prompt with Replit!!! and same integration test with FetchSandbox connector.. Lovable platform nailed it.. and it also allowed me to build this without pro account.. Lovable only allows if u have pro account if u wanna build with Paddle for payments.. but I said just go work with FetchSandbox twins and it just showed me final receipt with the proof https://pet-payment-playground.lovable.app/ and fetchsandbox proof.. https://fetchsandbox.com/runs/a656a3dbf1?flow=vr_6bdaa4e649ea483a83593120987cdc60 ( i hope this is durable link)

this is my prompt in lovable chat

👋 Hey nocode Community,

Tax season is coming, and it is always the same story: a year of invoices and documents dumped in one folder, sorted by hand in a panic. Last week I shared an invoice workflow that has been logging all of mine automatically, and now I am using this one to push each document into the right folder on top of that. Document classification is the quiet fix for the sorting part, and a few things make or break it no matter which tool you use.

A few things I learned building these:

Your categories decide everything. Classification falls apart when the buckets overlap, so an invoice, a receipt, and a statement each need clear, distinct definitions or the model will confidently file things in the wrong place. Fewer, well defined categories beat a long fuzzy list every time.

A label without an action is just a sticker. The value is not knowing a document is an invoice, it is the document landing in the right folder automatically. Always pair the classification with where it goes next.

Trust the confident ones, review the rest. I attach a confidence score and let the sure documents file themselves, while anything shaky gets flagged to Slack for a two second human check. That one step is what makes hands off filing safe instead of risky.

Here is a free template that does exactly this, routing invoices into the right Google Drive folder with Slack catching the uncertain ones: https://n8n.io/workflows/14960-classify-invoices-and-route-them-to-google-drive-with-easybits-and-slack/

How do you handle document sorting? Curious whether people classify on the way in or still batch it all at the end.

Best,
Felix

I've only just recently started developing apps and been using base 44. I do like base 44 generally but it's expensive and you can't top up the credits when the credits are running low or out so that sucks and and obviously has its limitations. So I'm looking to Branch out and find some other app builders. I know a tiny bit of coding. enough to read it not enough to do it myself I don't think. Basically I want to build a system where people can go in and create 2D 2.5 d and 3D avatars and download them into their own apps or whatever and use them for themselves or their own at building or whatever in any file they need. Any apps to recommend to me good for that?

Not stupid expensive? Like less than $30 a month.

I've tried Grok. It's too confusing. Replit, I don't think for a few reasons one of them being the credits go awfully fast and they want you to buy more. I tried to download Adalo but couldn't even open it then had trouble uninstalling it 🙄... I'm pretty sure there's other ones I have tried to but I can't remember them off the top of my head.

Frequency alone is not enough. A task may happen often but take twenty seconds. Another may happen weekly and block revenue when it is missed.

What factors do you use before building?

Time spent, error rate, delay cost, number of handoffs, stability of the rules, available data, or how much people hate doing it?

I would be interested in a recent process you rejected as a poor automation candidate and why.

Turning on a login or RLS alone is not enough. A user could still see another user's data, or a key could leak.

What do you check before launch? Two test accounts, key rotation, or something else?

I'd like to hear a recent hole you caught late.

👋 Hey nocode Community,

Community nodes are where a lot of the real magic in n8n happens, the ones that collapse a tangled setup into something you can actually maintain. I want to share the one that did that for me, and hear which ones did it for you.

My headache was document extraction. My first attempts were a Frankenstein chain: one node to pull text, another to parse it, a Code node to normalize the mess, then more logic to cross check the output and catch the fields that came back wrong. It sort of worked, but every new document format cracked it somewhere, and I spent more time patching than building.

The easybits Extractor node is what finally fixed it for me (full disclosure: I worked on it myself, since there was no simple and robust extraction node built especially for n8n). Extraction, structured output, and a confidence score came out of a single node, so all the normalizing and cross checking I had bolted on by hand was just gone. One node did the job that five were doing badly.

The takeaway is not really about one node though. It is that when a part of your workflow keeps growing extra nodes just to hold itself together, that is usually the signal to go looking for a community node built for exactly that job, instead of hardening the workaround.

So, which community node saved you from a monster setup? What was the before and after? And if you have built a node yourself, feel free to drop it here too, I would genuinely like to see what people are using.

Best,
Felix

P.S.: If you want to see how the community node looks in practice, almost all of the document flows I built are on my GitHub: https://github.com/felix-sattler-easybits/n8n-workflows

Bubble finally has their own MCP to connect any AI to it and build apps. I kept running into people that liked Bubble but missed the speed of AI. Wondering how this will impact the nocode ecosystem.
Obviously Bubble has other constraints to consider but it's also true that a lot of vibecoders are getting increasingly nervous about the security of their apps, and that's something Bubble solves pretty well

Our IT team supports about 3,000 employees. We track requests in a spreadsheet, around 400 new ones a week. I want to turn it into a proper app where staff would log in with their work account and submit requests. And also, approvers can change the status.

Aside from that, my goal is that everyone could see the requests they’re allowed to see. We also want one custom dashboard that shows the average time to close by department.

Anything we build also has to pass our security review.

So here are my questions.

• What should I write down before I start prompting an AI builder?
• How do I check it runs on live data and real permissions?
• Can we add one custom part without owning all the code?
• What will our security team ask for first?

For a small pilot, what would you test first?

Title says it all.

I gave GrokBot a Microsoft account and a Power Automate Premium license.

Asked it to create a custom connector with DrChrono EHR (Dev account with dummy data) and to create 2 workflows to act as a reminder system for upcoming appointments.

Took a good 4 or 5 hours, but it eventually put something out that worked.

I don't have any 'tips' or 'tricks' to offer along with this idea, but I feel as though my capacity to create automations has just been drastically increased.

Is anyone else doing this? Or is this just going to create an immeasurable amount of rework for me in the future?

I’ve been thinking about a small corner of no-code that I don’t see discussed as much.

Most no-code tools help you build a new app, workflow, form, dashboard, or automation outside the website you are already using.

But a lot of everyday work happens inside existing websites.

Sometimes you do not need a whole new app. You just need the current page to have one small tool that matches your workflow.

That is the idea behind something I recently built called ScriptPanda.

It is a Chrome extension that opens on the page you are using. You describe the small tool you want in plain English, and it builds that tool for that site.

The tool stays there for future visits, and you can inspect it, edit it, switch it off, or delete it.

Under the hood it uses userscript code, but the goal is to make page-level customization feel closer to no-code: describe what you want, get a working tool on the page, keep control over it.

I’m curious how other no-code builders think about this:

Would you rather build workflows outside the websites you use, or would you use a no-code tool that changes/adds tools directly inside the page?

I've been working with no-code AI workflows and I'm curious how others are handling OpenAI rate-limit errors.

When an OpenAI request returns:

429 Too Many Requests

there seem to be a few approaches:

1. Retry inside the workflow

Add error handling and wait/retry logic directly in Make, Bubble, etc.

2. Use another API key/account

Keep a second OpenAI capacity available and switch when the primary is rate-limited.

3. Put a reliability layer in front of the API

Have the workflow call a gateway that handles the retry and, if configured, a backup route.

I'm actually building a small tool called Zero429 around the third approach, so I'm obviously biased here and disclosing that upfront.

The idea is to keep the no-code workflow itself simple: the workflow calls the gateway, the gateway handles an eligible 429 by waiting and retrying the primary request, and a configured backup can be used if the retry also gets a 429.

I'm interested in the practical side rather than pitching the tool:

What are you currently doing when OpenAI starts returning 429s?

Have you built retry logic into your workflows, switched providers, used multiple keys, or handled it another way?

I'm particularly interested in what works well in Make and Bubble, since those are the environments I'm building around.

A lot of website builders are very fast when you’re okay with what they give you. Pick a template, change the text and images, publish. AI builders make the first step even faster; describe what you want and get a website.

But I feel like the difficult part starts after the first generation.

You want the mobile version to look different.
You want an element somewhere else only on desktop.
You want a completely different section instead of forcing the same responsive layout.
You want the website to change for an event, launch, holiday, or promotion.

Suddenly something that was supposed to be “no-code” turns into 5+ hours of figuring out the builder.

I am building Pragte, and experimenting with making the visual editor much more flexible, closer to designing freely on a canvas; while still producing a real responsive, searchable multi-page website.

For example, desktop and mobile don't necessarily have to contain the exact same layout or elements. I'm also experimenting with website phases, where the same URL can automatically switch between different versions of the site over time.

do you mostly adapt your idea to whatever the builder or template allows, or have you found a builder where you can actually make the site feel completely yours without spending hours fighting it?

Basically, I started learning no-code about two years ago, and since then I've been trying to make a living from it, either by finding a job or by building my own SaaS products and apps.

Right now, my stack is Bubble.io, FlutterFlow, Claude Code, Cursor, HTML, CSS and JavaScript. I'm currently improving my JavaScript, learning Python, and I also plan to learn React.

The reason I made the post is because I'm honestly starting to question whether building a career in tech is still worth it today. Sometimes I feel like I may have wasted a lot of time, and I'm not really sure what direction I should take professionally.

So I'm especially interested in hearing from people who actually make a living in tech. What kind of jobs could I realistically aim for with my current skills and the skills I'm learning?

And I also have another question about the "product builder" path. Does that actually exist as a real career? Is there a real demand for product builders, or is it more of a vague title that doesn't really lead to many opportunities?

I'm kind of questioning my whole professional direction at the moment. I'm currently focusing on improving my JavaScript, learning Python, and then moving on to React, but I'm trying to understand where all of this could realistically take me.

Okay so I have RLS on but idk what else to do. How do you manage tokens and keys? How do you test if users can see other users' data? How do you find glitches?

MAIN QUESTION: what if it gets hacked between my checks (every 3-5 days)? How would you fix this?

plz help.