← Back to all sparks
T

Teable

COLLAB
Velocity10.0

Open-source no-code database and Airtable alternative

Teable is becoming an event-driven AI workspace — cross-app triggers and credit-billed tool calls mark a real capability shift.

ai-workspaceno-code-databaseevent-driven-automationopen-sourceagentic-workflowsoauth-ecosystem
◆Current state
Teable is an open-source, self-hostable database that has accumulated substantial AI-native capabilities over the past months — App Builder for no-code application construction, AI Routines running as long-running agentic tasks, and now event-driven automation that bridges third-party integrations into those routines. The product ships at roughly 2–3 releases per week, spanning both features and bug fixes, and its OAuth app ecosystem is maturing with audit log coverage and in-app notifications that signal multi-team enterprise deployments. The removal of routine max-duration limits (Sep 17) and event-triggered automation (Sep 20) landed in close succession, which makes the direction unmistakable.
◆Where it's heading
Teable is converging on a position between Airtable (structured data), Notion (collaborative workspace), and lightweight automation tools — differentiating on AI-native routines and open-source deployability. The event-triggered automation layer, payload access during execution, and credit-billed third-party tool calls point toward Teable positioning itself as an agentic workflow engine where AI can respond to real-world triggers without time constraints. The Composio integration and BrightData scraping support suggest the platform is deliberately targeting data-intensive automation use cases that are out of reach for simpler no-code tools.
◆Prediction
Expect broader event-type coverage across Composio integrations and conditional logic on incoming event payloads — the current implementation is one-trigger-per-automation with full payload passthrough, and adding filter/branch rules is the obvious next step. The Sheet form designer regression noted in Sep 19 is a marker of technical debt on the form layer that will need resolution before the App Builder story is complete.

◆Recent moves

  1. 1d ago

    Account data export before deletion, community support link

    Support surface update (Community form replaces anonymous form) and a user safety net (data export before account or space deletion). Neither changes the capability surface; these are operational completeness items that indicate Teable is managing a growing user base that needs formal off-ramps.

    View source ↗
  2. 3d ago

    OAuth apps gain in-app notifications and subscription awareness

    Teable's OAuth ecosystem gets two meaningful upgrades: apps can push consent-gated, revocable notifications to users, and can query subscription and license status. The audit log expansion — covering membership and role changes — indicates Teable is being used in environments where compliance accountability matters, not just personal productivity.

    View source ↗
  3. 3d ago

    AI sandbox gets maintenance controls and per-task model tier selection

    Operational maturity additions to Teable's AI layer: admins can throttle sandbox access during maintenance without killing in-flight sessions, and agents can select a model tier per scheduled task. These controls suggest Teable's self-hosted customers are running AI routines at meaningful scale where resource management matters.

    View source ↗
  4. 6d ago

    release.2026-09-22T03-34-15Z.3202

    A billing leniency feature — custom domains stay active for one week after Business plan expiration with owner notifications. Reduces churn friction at the plan boundary; no capability change.

    View source ↗
  5. 6d ago

    release.2026-09-21T14-48-39Z.3197

    Two correctness fixes: numeric lookup sort order and lookup grouping for linked records. AI conversation stability during model switching also patched. Routine maintenance work across the data layer and AI engine.

    View source ↗
  6. 7d ago

    release.2026-09-21T07-48-52Z.3187

    The welcome page chat editor brought in line with regular chat — same menu options, file manager access, and slash commands. Reduces interface inconsistency for users who treat the welcome page as a primary chat entry point.

    View source ↗