Update Record

Update record in Bubble is a workflow action called "Make changes to a thing" that modifies an existing database record. It changes one or more fields on a specific record without creating a new one.

This action is fundamental to any app that lets users edit their own data. Profile updates, status changes, order edits, and setting adjustments all rely on update record logic in Bubble.

Key Takeaways

• Modifies existing data: The update record action changes fields on a record that already exists in your Bubble database without deleting or replacing it.
• Called "Make changes to a thing": In Bubble's workflow editor, this action is listed as "Make changes to a thing" rather than "update record."
• Requires a specific record reference: You must tell Bubble exactly which record to update, not just which data type. Vague references can update the wrong record.
• Can update multiple fields at once: One "Make changes to a thing" action can modify several fields on the same record in a single workflow step.

What is Update Record in Bubble?

Update record in Bubble is the "Make changes to a thing" workflow action. It selects a specific database record and modifies one or more of its fields. The change is permanent and replaces the previous field values immediately.

When a user edits their profile, changes a setting, or updates a form they submitted earlier, your app needs to write the new values to the existing record rather than create a duplicate. That is exactly what this action does.

• Targets a specific record: You specify which record to update using a reference, typically the current user's record, the record a page is loaded with, or a record from a search result.
• Fields are updated individually: Inside the action, you choose which fields to change and assign the new values, leaving all other fields on the record unchanged.
• Changes take effect immediately: Once the workflow runs, the database record is updated in real time. Any elements displaying that data on screen refresh to show the new values.

Understanding the difference between creating a new record and updating an existing one is one of the most important fundamentals in Bubble's data model.

How Update Record Works in Bubble

To update a record in Bubble, add a "Make changes to a thing" action to any workflow. Specify the record you want to modify, then choose which fields to update and what values to assign to them.

The action is available in the workflow editor under the Data category of actions. Setting it up correctly requires knowing which record you are targeting before you configure the field changes.

• Choose the thing to change: The first field in the action asks which record to modify. Reference it clearly, for example "Current User" or "Current Page's Order" rather than a broad search.
• Set field values: For each field you want to update, choose the field name and enter the new value. You can use dynamic expressions to pull values from inputs, the current user, or other data sources.
• Multiple fields in one action: You can add as many field changes as you need within a single action, keeping your workflows clean rather than stacking multiple update actions for the same record.

After the action runs, Bubble updates the database instantly. If you have elements on the page displaying the updated record's data, they refresh automatically without requiring a page reload.

Why Update Record Matters for No-Code Apps

Update record is how your Bubble app allows users to change their own data over time. Without it, every change a user makes would require deleting the old record and creating a new one, which is destructive and loses history.

Apps are not static. Users need to edit profiles, change preferences, update orders, and revise submissions. Update record is what makes all of that possible cleanly.

• Enables self-service editing: Users can update their own information without contacting support or having an admin make changes manually in the database.
• Preserves record identity: Updating a record keeps its unique ID intact, so all relationships and references to that record in other data types remain valid after the change.
• Supports status workflows: Apps with approval flows, order statuses, or task states use update record to move items through stages by changing a status field on the existing record.

Every app that collects and stores user data eventually needs users to be able to change that data. Update record is the mechanism that makes self-service data management possible in Bubble.

Common Update Record Mistakes in Bubble

The most common update record mistakes in Bubble are updating the wrong record because the reference is too broad, updating a field without first validating the new value, and forgetting to restrict which users can trigger the update workflow.

Getting the record reference wrong is the most dangerous mistake because it can silently update the wrong user's data without any obvious error message.

• Vague record references: Using a search to find the record inside the update action can return unexpected results if the search is not specific enough. Always reference the exact record directly where possible.
• No permission check: Anyone who can trigger the workflow can update the record unless you add a condition that checks the current user has permission to make that specific change.
• Missing validation before update: Updating a field with an empty or invalid value from an input can corrupt your data. Validate inputs before the update action runs to prevent bad data from being saved.

Adding privacy rules in Bubble alongside your update workflows ensures that users can only modify records they are supposed to change, adding an important security layer beyond frontend workflow conditions.

Conclusion

Update record is one of Bubble's most used and most important workflow actions. It is how every edit, status change, and profile update gets saved in your app. Targeting the right record with the right permissions and validation in place is what keeps your database clean and your users' data safe. At LOW/CODE Agency, we've helped 450+ clients build and scale apps on Bubble and other no-code platforms. Our clients include global brands like Medtronic, American Express, Coca-Cola, Zapier, and Sotheby's.

Frequently Asked Questions

How do I update a record in Bubble?

Add a "Make changes to a thing" action to a workflow. Choose the specific record to modify, then set which fields to change and their new values.

What is the difference between "Create a new thing" and "Make changes to a thing" in Bubble?

"Create a new thing" adds a new record to your database. "Make changes to a thing" modifies an existing record without creating a duplicate.

Can I update multiple fields in one Bubble workflow action?

Yes. The "Make changes to a thing" action lets you update as many fields as you need on the same record within a single workflow step.

How do I make sure I update the correct record in Bubble?

Reference the record directly, such as "Current User" or "Current Page's Thing," instead of using a search inside the action, which can match unintended records.

Can I restrict who can update a record in Bubble?

Yes. Add an "Only when" condition to your workflow to check that the current user has permission. Also configure privacy rules on the data type for backend protection.

Does updating a record in Bubble change its unique ID?

No. Updating a record modifies its field values but keeps its unique ID unchanged. All references to that record in other data types remain valid.