I’ve been using Claude to help me troubleshoot and understand development on Bubble, and that has improved since Claude became able to access the web, because the results are so much more relevant than than googling and searching through forums. It’s like a responsive rubber duck. But Claude still has trouble understanding how to construct expressions in Bubble’s format, often showing a fundamental lack of understanding of how Bubble allows you to access data and data relationships. This is somewhat surprising, since Claude is apparently powering the AI app generation functionality.
My question is, @Bubble, are there any plans to cross pollenate with Claude so that it can be used in both directions?
Thank you for the suggestion. Personally, I prefer Anthropic’s stated commitment to ethical practices (yes, I’m aware that mere words are not trustworthy, but I do prefer to do business with organizations who at least acknowledge the ethical ramifications,) and unless Bubble plans to switch to OpenAI internally, I still think it would make sense for Claude to be updated to handle Bubble syntax. I’d love to hear suggestions on how to improve the Claude integration.
Awesome!
I don’t know if it helps, but I gave Claude some links to Bubble docs and asked it to create a summary for itself to use as a reference in a Project’s knowledge artifacts, and published the result: Claude Artifact
Thank you. I do wonder if Bubble has any intentions of working with Anthropic to train Claude better, considering that they’re using Claude to build AI apps.
Full example response to 'how are the app, user, and agency types related?'
Great question! In **NQU Secure**, the **App**, **User**, and **Agency** data types are tightly interconnected to support multi-tenant security management, collaboration, and access control. Here's a clear overview of how they relate:
1. Agency
Represents an organization or development agency.
Owns or manages multiple Bubble apps.
Has multiple Users as members or admins.
Fields:
Apps (list of Apps the agency manages)
Admins (list of Users with admin rights)
Members (list of Users who are general members)
Invited Users (pending User invitations)
2. User
Represents an individual user of NQU Secure.
Can belong to an Agency (via the Agency field).
Can be invited to multiple Agencies (Invited To Agencies list).
Can own or collaborate on multiple Apps:
All Apps (all apps the user is associated with)
Verified Apps (apps the user has verified ownership of)
Pending Apps (apps awaiting user action)
Has a User Type (option set: Admin, User, Backup) controlling permissions.
3. App
Represents a Bubble application connected to NQU Secure.
Can be owned or managed by an Agency (Agency field).
Can be linked to multiple Users:
Verified Admins (users verified as admins of the app)
Verified Collaborators (users verified as collaborators)
Has a Found By field indicating the User who added/discovered the app.
Can be shared with an Agency so all agency members/admins can collaborate on it.
How They Work Together
Relationship
Description
Agency ↔ Apps
An Agency manages multiple Apps. The Apps field in Agency links to these.
Agency ↔ Users
An Agency has Admins and Members (Users). Users can belong to one Agency (Agency field).
User ↔ Apps
Users can own, verify, or collaborate on multiple Apps.
App ↔ Agency
An App can be linked to an Agency, meaning the Agency manages or owns it.
App ↔ Users
Apps have lists of Verified Admins and Collaborators (Users).
User ↔ Agency Invitations
Users can be invited to Agencies (Invited To Agencies), and Agencies track invited users.
Visual Summary
[Agency]
| owns/manages
v
[App] <---- verified/administered by ---- [User]
^
| linked to
[Agency]
[User]
| belongs to
v
[Agency]
Practical Example
Acme Dev Agency (Agency)
Has Alice (Admin User) and Bob (Member User)
Manages BubbleApp1 and BubbleApp2 (Apps)
BubbleApp1
Linked to Acme Dev Agency
Alice is a Verified Admin
Bob is a Verified Collaborator
Alice belongs to Acme Dev Agency, has access to BubbleApp1 and BubbleApp2
Bob belongs to Acme Dev Agency, collaborates on BubbleApp1
Why This Matters
This structure allows:
Agencies to centrally manage multiple apps and team members
Users to collaborate across apps and agencies with appropriate permissions
Apps to be securely audited and managed by multiple users and agencies
Granular access control and context-aware vulnerability scanning
In short:
Agencies group Users and Apps.
Users belong to Agencies and collaborate on Apps.
Apps are linked to Agencies and Users for ownership, collaboration, and security management.
Let me know if you’d like a diagram or have questions about specific workflows!
Full example response for 'How do users add an app to NQU Secure'
To add a Bubble app to **NQU Secure**, users follow a guided, multi-step process designed to verify ownership and configure access for security scanning. Here's a clear overview of how users add an app:
How to Add a Bubble App to NQU Secure
1. Initiate the Add App Process
From the Dashboard or Apps page (componentApps), click the “Add app” button.
This opens the popupAddApp modal.
2. Enter App Details
Provide your Bubble app’s URL in the “App URL” input.
Use the run-mode URL (e.g., https://yourapp.bubbleapps.io or your custom domain).
If your app is password protected, toggle the “This link is password protected” option.
Enter the username and password in the additional fields that appear.
3. Verification Step
Click “Verify”.
NQU Secure will:
Check if the URL points to a valid Bubble app.
Confirm the app is not already claimed by another user.
Validate credentials if provided.
Status messages will guide you:
If the app is not a Bubble app, an error appears.
If the app is already claimed, you’ll be notified.
If successful, you’ll see a success message indicating the app is connected.
4. Verify Ownership (if required)
For some features, you may need to verify ownership of the app.
This can be done via the popupVerifyAppOwnership popup, offering methods like:
Email verification (sending a code to a domain-matching email).
Adding a verification page to your Bubble app.
Inviting NQU Secure as a collaborator.
Follow the instructions in the popup to complete verification.
5. Configure Connection Settings (Optional but Recommended)
Set run-mode credentials if your app requires login.
Grant collaborator access (view or run-as) for deeper scans and backups.
Complete the Connection Wizard checklist to enable all features.
6. Start Using NQU Secure
Once added and verified, your app appears in your Apps list.
You can now:
Run vulnerability audits.
Set up automated backups.
Manage test users for privacy rule testing.
View and edit app metadata.
Summary
Step
Action
Open Add App
Click “Add app” button
Enter URL & Credentials
Provide app URL, optional username/password
Verify
Click “Verify”, wait for confirmation
Ownership Verification
(If prompted) Use email, page, or collaborator method
Configure Access
(Optional) Complete connection wizard, set credentials
Use NQU Secure
Run audits, backups, manage users, view insights
Tips
Use the run-mode URL (not the editor URL).
Credentials are optional but unlock more thorough scanning.
Ownership verification may be required to access sensitive features.
No collaborator access is required for basic scans, but granting it enables advanced features.
This streamlined process ensures you can quickly connect your Bubble app to NQU Secure, verify ownership securely, and start protecting your app with powerful vulnerability scanning and backup tools.
The above responses have no user input/customisation. It’s all auto-created. The goal here is to have auto-documentation for any Bubble app, which you can talk to directly or copy the entire documentation as Markdown to paste into any LLM of your choice or use for internal reference.
this looks cool, especially the part where it seems to incorporate the elements names and workflow actions etc.
Is this going to only be something available as a ‘look at my entire app and create documentation’ or are you going to add it to an extension so in the editor we can ask it to document a certain part of the app and see that documentation and make any necessary edits in real time before we save or copy/paste.
Real-time docs, yes, but only with collaborator access for technical reasons
Chat is the intended ‘medium’ for using these docs (the only reason long form technical docs exist is that that was the best way to understand something. Now, you don’t need that - you can just ask what you want to know and the AI will handle the organisation for you). The long form technical docs exist, but mainly so that you can copy your entire documentation as Markdown and save/use anywhere with an LLM of your choice.
I think my results would be as good if I put effort into it, which I have no interest in doing. Obviously I wouldn’t feed the whole thing, but you already knew that.
