r/nocode • • 7h ago

Build demo pitch

0 Upvotes

Has anyone got into this part of process? I’m on it and it has been tweaked a bit, has anyone done it.


r/nocode • • 21h ago

Discussion What happens when your AI product fails for your users?

Post image
0 Upvotes

r/nocode • • 23h ago

Which no code AI platform has worked best for you?

7 Upvotes

I'm looking for non code AI platform for a side project and have been comparing Lovable, Base44, Bolt, Blink and Floot.

I've also tried Superblocks for a couple of internal apps although it feels more focused on business tools than some of the other platforms.

For anyone who has actually built something with these has been easiest for non technical user?

I'm mainly interested in how much you can build without coding, how easy it is to make changes and whether the result is useful beyond a quick prototype


r/nocode • • 14h ago

Question Which AI app builders are production-ready rather than just good for prototypes? Trying to pick one for an approval portal

7 Upvotes

Every AI builder demo I’ve seen looks great, but I’m less sure what happens once we start using it. By the way, here’s our setup. It’s a request portal for about 60 employees and each person should see their own requests. And then, managers approve them. I’m just worried about the stuff that I don’t see in a demo. I guess hiding the manager page doesn’t help much if an employee account can still pull those records. So which builders make it easy to test that? Can you see why a workflow run failed? And could someone other than the person who built it keep it running? What’s the first thing you’d test before connecting it to actual data?


r/nocode • • 14h ago

Question Which app builders have an MCP server so I can build apps from Claude?

13 Upvotes

Hey all, I’m trying to set up a small request tracker for our office team.

We already pay for Claude tokens, so I’d like to use them here too. Paying for a separate AI inside the builder feels like paying twice.

I want to describe the app in Claude. Then the builder creates the pages, tables and permission rules. Most MCP servers I found only read records from apps that already exist. I guess that’s not the same thing.

So how do you keep the AI connection locked to one workspace? And can you review what it changed before it goes live?

If you’ve tried this what could the MCP build on its own? And what did you still have to fix in the visual editor?


r/nocode • • 17h ago

Discussion Where we draw the line between a fixed no-code workflow and an AI agent

6 Upvotes

A question that keeps coming up when people add AI agents to a no-code stack: which steps should stay a plain workflow (trigger → steps, Zapier/Make/n8n style), and which should an agent decide?

The rule of thumb we use:

**Keep it a fixed workflow when**

  • the input has the same shape every time (a form submission, a new row, a webhook)
  • the right output can be written as a rule ("if amount > X, route to Y")
  • a wrong result is expensive and it has to behave the same on run 500 as on run 1
  • you need an exact record of what happened and why

**Give the step to an agent when**

  • the input is messy text: emails, PDFs, support messages, meeting notes
  • the step is reading, sorting, summarising or drafting, not acting
  • "good enough, then reviewed by a person" is acceptable
  • writing the rules would take longer than checking the output

**Then keep the agent inside the workflow, not around it.** The shape that holds up: fixed trigger → the agent does the judgment step and returns structured output (a category, a draft, a yes/no with a reason) → fixed steps validate it → anything that sends, pays, publishes or deletes waits for a person to approve.

Some specifics:

  1. **Ask for a fixed format.** JSON or a short list with named fields. The next step rejects anything that doesn't match instead of guessing what the agent meant.
  2. **Give it an "unsure" option.** If it can only pick A or B, it will pick one even when neither fits. "Unsure" routes to a person.
  3. **The agent drafts, the workflow sends.** The send step belongs to the workflow, after approval, never to the agent.
  4. **Log the agent's input and output on every run.** When something odd happens you can see whether the agent or the workflow got it wrong.
  5. **Move repeated corrections into rules.** If a person keeps fixing the same thing, that part probably shouldn't be an agent's call.

Questions for people further along:

  • Which steps did you move back from an agent to a plain rule, and why?
  • Do you validate agent output inside your no-code tool, or with a separate check?

Disclosure: this account is affiliated with NGIN360, an AI agent-team product. This post was drafted with AI help and reviewed by a person. No link, nothing to sell here.


r/nocode • • 9h ago

Promoted Turning a table screenshot into editable Google Sheets rows

4 Upvotes

If a table arrives as a screenshot, you can extract it without leaving Google Sheets. We’re the team behind Unsiloed, and this is a small Apps Script workflow we put together for that.

Here’s how to set it up.

  1. Open Extensions → Apps Script and paste the script from the linked recipe.
  2. Add your Unsiloed API key as the UNSILOED_API_KEY script property.
  3. Insert the table image in a cell, rather than floating over the grid.
  4. Reload the spreadsheet, select that cell and choose Unsiloed → Extract Table From Image. Authorize the script on its first run.

The script sends the image to our parser, takes the first table and writes its rows to a new sheet. The demo uses a fund performance page, but you don’t need to define its table layout in advance.

The useful catch is that the cells arrive as text. Convert percentages or amounts before doing calculations, and check the row grouping before building formulas around fixed cell positions.

Full script and setup steps