Have something to say?

Tell us how we could make the product more useful to you.

Stuck in an implementation loop

I have been trying to implement a Google photos Read for about 100 credits. We keep going back and forth between settings and I've been working on this for a few days now and it's just an infinite loop over and over and over. I am asking for a good faith credit rebate at this point. I am not sure why the AI cannot fix the issue. What should be a simple oauth implementation is turning out to be a nightmare. Maybe a human can take a look at it and see what it's broken. I'm going to continue working today but I burned through a lot of my credit's working on this same exact issue and it seems like the AI keeps asking me the same thing. Make sure the ID is right make sure my secret is right. Over and over make sure the website call back is correct. I'm not an expert developer but for some reason I feel like the issue is definitely on our side. What happens is when I go to click connect to Google photos we're supposed to pull down or read the photos what happens is the callback page comes up and immediately jumps me back to my qlimpse.com/vault page. Very frustrating at this point please help

Mark Romano about 3 hours ago

💡

Feature Request

Workspace Level Agent/Bot chat window that we can tell it to update multiple apps at the same time based on strict fields and options

i'm not sure if this is a feature and i just missed it, so if so i do apologize. I have spent the entire afternoon going back and forth in two different apps i built here in the site. my question is this.. i was doing the same thing for both sites, so is there a way to create a workflow that would allow for me to talk to an agent or bot of some kind and tell it to update the features in both apps at the same time... i'm thinking time saving with this.. efficient is effective! effective is $$$$$$ The response from the AI makes sense… however @Base44 this would be something you could add as a feature.. as long as the sites are all in the same workspace, allow the ports/protocols to communicate for “sync” like features with very spefic user input required to keep things secure. checks and balances and verifications thru API keys or something would be AMAZING!!!! Imagine… Our Dashboard with all the apps, then an AI chat box right there that i can chat within my Workspace.. maybe later you add the ability to expand to other connected workspaces… from there I can tell the agent, Hey i want you to look at SiteA and compare it to Site2, look for the common settings that are in the function of event sign up, selecting forms, in kiosk modes, event sign ups, etc.. and identify how we can optimize them both at the same time as it relates to each of their sites. Its a real PITA to copy paste the output consistently between multiple builds on here… centrally managed in that fashion would be ACE!!!!!!! If you love and use my idea and nobody else said it before, help me out with some free top tier membership for a term TBD.. nothing out of your pocket, just a free membership and you get one hell of a feature that you could probably make a business model out of! Sell it at a premium teir or something. See I’m such a team player I’m giving away all the angles… :) And if you read this far.. at least let me know and see if you got a smile out of it! Happy Friday peeps! oh.. and if someone else had the idea already.. Kudos to you? Then the question is to @Base44 to deliever! :) Thanks much!!! ____________________________________ This is the support bot chat response…. 5:03 PM Great question, and no need to apologize — this is a really smart thing to think about! Here's the honest answer: Base44 does not currently have a built-in feature that lets you apply changes to multiple apps simultaneously from a single chat or workflow. Each app has its own AI chat that works independently. However, there are a few practical approaches you can use to save time: 1. Use App Templates (Most Efficient) If the two apps share a lot of the same structure, you can turn one into a Workspace Template and create new apps from it. Future updates would still be manual, but you'd have a solid shared starting point. → Dashboard → Settings → App Template 2. Copy-Paste Prompts Across Both Chats Not glamorous, but effective: write your update prompt once, then paste it into each app's AI chat. Since you're doing the same thing in both, this cuts your thinking time in half. 3. Use Superagents (Closest to What You're Describing) Base44's Superagents can connect to tools and automate workflows — but they work at the workspace level, not across apps simultaneously. They can't push code changes to multiple apps at once, but they could help you orchestrate other tasks. 4. Clone & Sync Strategy If both apps are very similar, you could maintain one "master" app and clone it when you need a second version. The downside is keeping them in sync over time. The feature you're describing — a single agent that updates multiple apps simultaneously — doesn't exist yet, but it's a great idea worth submitting to the Base44 feedback board so the team can consider it! Would you like help setting up a template or cloning workflow to make this easier going forward?

Apps@ZFG about 17 hours ago

1
💡

Feature Request

Make Two-Factor Authentication (2FA) mandatory a possibility

Two-Factor Authentication (2FA) for End Users of Built Tools I’d like to request built-in Two-Factor Authentication (2FA / MFA) support for the end users of applications created with Base44. For many real-world use cases, a simple email + password login is no longer sufficient—especially when apps handle sensitive data, internal workflows, or customer accounts. Having native 2FA support would significantly improve the security and professionalism of tools built on Base44. Key capabilities that would be highly valuable: Support for authenticator apps (e.g. Google Authenticator, Microsoft Authenticator, Authy) using TOTP codes Optional fallback methods like email codes or SMS codes Ability to enable 2FA per app Option to enforce 2FA globally, or only for specific roles / sensitive areas Backup/recovery codes for account access if a device is lost A clean, built-in UX flow for setup, verification, reset, and recovery Why this matters: Security for production apps Many Base44-built tools are used beyond prototyping. Once real users and data are involved, stronger authentication becomes essential. Trust and credibility Offering 2FA increases confidence for both internal users and external customers. Protection against compromised passwords Even if credentials are leaked or reused, a second factor adds a critical layer of protection. Essential for B2B and sensitive use cases MFA is often expected (or required) for admin panels, internal tools, and customer-facing platforms. Ideal implementation: A native, easy-to-configure solution inside Base44, without requiring custom auth setups or external integrations. For example: Toggle to enable 2FA Select authentication methods Optionally enforce it based on roles or app sections In short: Base44 should provide built-in 2FA/MFA for end users of created apps—preferably with authenticator app support, optional fallback methods, and simple configuration. This would make Base44 much more suitable for secure, production-grade applications.

Diogo Feleciano 2 days ago

💡

Feature Request