1. Allow databases, apps, and automations to be moved between bases without breaking dependencies
I really need a proper way to move databases, apps, and automation scripts from one base to another.
As a project grows, it is very normal to start with separate bases and organize things later. For example, I might create several databases for different parts of the same website or project in separate bases while experimenting. Later, I may want to bring everything into one clean, organized base.
Right now, this becomes a major problem because the individual pieces cannot simply be moved or transferred.
More importantly, these things often have dependencies. A database may be connected to another database. An app may depend on several databases. An automation script may read from one database and write to another. If I move only one piece, those connections can break.
I think the ideal behavior would be:
- I select a database, app, or automation and choose Move to another base.
- Teable detects all of its dependencies and connected resources.
- If dependencies exist, Teable clearly warns me:
This item has dependencies.
Moving it alone may break connections with other databases, apps, or automations.
The following connected resources also need to be moved:
Database A
Automation B
App CDo you want to move all connected resources together?
- If I confirm, Teable moves the entire dependency tree and automatically preserves the connections.
This would make reorganizing a workspace dramatically easier.
I don’t think this is just a convenience feature. For anyone using Teable to build real projects, the ability to restructure and reorganize a system without rebuilding everything is extremely important. I would really like to see this considered for the priority roadmap.
2. Support authenticated browsing/scraping for websites that require login
I also really need a better solution for collecting data from websites where the content is publicly visible but the website requires you to be logged in to access more of it.
X is a good example.
Suppose I want to collect the last 1,000 posts from a public X profile. Without logging in, I may only be able to access a small portion of the profile before X starts requiring authentication. The data itself isn’t necessarily private, but access to it is behind a login wall.
The same problem exists with other websites and social platforms.
What I would love to see is some form of authenticated scraping/browser session support.
For example, Teable could provide a secure browser environment where I can authenticate myself once, and then a scraper can use that authenticated session when collecting data.
Something like:
Connect authenticated browser session
Open a secure browser window → log in to X → authorize the session → use this session for scraping.
I could use a dedicated account specifically for this purpose.
Another possible approach would be managed browser profiles or persistent headless browser sessions. The important part is that the scraping process should be able to access websites as an authenticated user instead of being limited to the tiny portion of data available to anonymous visitors.
This would be incredibly useful for research and data workflows. For example:
- Collect the last 1,000 posts from an X profile
- Monitor posts from specific accounts
- Collect data from Reddit pages that require authentication
- Extract information from websites where more content becomes available after login
- Run scheduled scraping jobs using a persistent authenticated browser session
Of course, this should respect each website’s terms, permissions, and access controls. I’m not asking for a way to bypass private content or security. I’m asking for a supported way to use an account that I have legitimately authenticated with, so Teable can work with content that is available to that authenticated session.
This is one of the biggest gaps I currently run into when building data workflows in Teable. Authenticated browser/scraping support would unlock a huge number of practical use cases, especially for research, monitoring, competitive analysis, and content intelligence.
I would really appreciate seeing both of these features considered seriously for the priority ship queue. They would solve real workflow problems rather than simply adding convenience.