Databases
Sometimes a document isn’t the right shape for your information. When you have many similar things — a list of leads, a product inventory, a content calendar, a roster of vendors — you want a table: rows that all share the same columns, where each column means something specific. That’s what Databases are for.
A BridgeApp database looks like a spreadsheet at a glance, but it’s sturdier. Each column has a defined type — a date column only holds dates, a money column only holds amounts — so your data stays clean, sortable, and filterable. And because it lives inside BridgeApp, it’s collaborative by default and can plug straight into your automations.
Database vs. spreadsheet
Section titled “Database vs. spreadsheet”A loose spreadsheet lets any cell hold anything, which is flexible right up until it isn’t — dates typed five different ways, totals that don’t add up, a stray word in a number column. A database asks you to define your columns up front, and in return it keeps every row consistent and ready to filter, sort, and automate.
What you can do
Section titled “What you can do”- Define your own structure. Add the exact fields you need, each with a type.
- Enter data as a team. Add and edit rows together; everyone sees the latest.
- Filter and sort instantly. Narrow thousands of rows to the handful you care about. See Views & filters.
- Connect it to automation. Have an automation create a row when something happens, or a flow read rows to make a decision. See Connecting your data.
The pieces
Section titled “The pieces”| Term | Plain meaning |
|---|---|
| Database | A single table of structured records. |
| Attribute (field / column) | A named, typed column — like “Status” or “Amount”. |
| Entry (record / row) | One item in the table, with a value for each field. |