Database
The Database section in DotPortion provides a visual interface to explore and manage your data, similar to tools like MongoDB Compass. It allows you to:- View databases and collections
- Read documents
- Create new records
- Update existing records
- Delete records safely
Supported Databases
DotPortion currently supports:- External MongoDB (via MongoDB URL secret)
- DotPortion Platform Database (managed MongoDB)
Database Explorer UI
📁 Database Explorer (UI Reference)
The Database Explorer lets you select:
- A database connection
- A database
- A collection
Browsing Collections
After selecting a database:- All available collections are listed
- Each collection shows document count (when available)
- Clicking a collection loads its documents
Reading Data
📄 Read Documents (UI Reference)
You can:
- View documents in JSON format
- Expand and collapse fields
- Scroll through records
- Inspect values for debugging
- Verifying workflow outputs
- Debugging database logic
- Understanding data shape
Creating Data
➕ Create Document (UI Reference)
You can create new documents by:
- Selecting a collection
- Providing a valid JSON object
- Saving the document
Updating Data
✏️ Update Document (UI Reference)
You can update documents by:
- Editing existing fields
- Adding new fields
- Modifying nested values
Deleting Data
🗑️ Delete Document (UI Reference)
You can delete:
- Individual documents
- Selected records (where supported)
Platform Database vs External MongoDB
| Feature | Platform Database | External MongoDB |
|---|---|---|
| Setup | No setup required | Requires MongoDB URL secret |
| Management | Fully managed | User-managed |
| Access | Project-scoped | External cluster |
| UI Experience | Same | Same |
How This Relates to Workflows
- Database UI is for manual inspection and management
- Database Nodes are for runtime execution
- Both use the same underlying data
- Changes made in UI affect workflows immediately
Security & Permissions
- Database access is project-scoped
- Secrets are required for external databases
- Only authorized users can modify data
- Credentials are never exposed
Best Practices
- Use UI for debugging and inspection
- Avoid frequent destructive changes in production
- Prefer workflows for automated operations
- Validate data shapes before inserting records
- Use separate databases for dev and prod
Important Notes
- UI actions directly modify the database
- There is no automatic rollback
- Large collections may be paginated
- Performance depends on database size and indexes
Summary
| Action | Supported |
|---|---|
| View collections | Yes |
| Read documents | Yes |
| Create documents | Yes |
| Update documents | Yes |
| Delete documents | Yes |