Skip to main content
News

New: Interface extensions SDK releasing to open beta

  • September 10, 2025
  • 36 replies
  • 9558 views
Show first post

36 replies

Ruchika_Abbi1
Forum|alt.badge.img+17
  • Ruchika_Abbi1
  • Inspiring
  • November 11, 2025

This looks amazing! Is it possible to use Github&Netlify, i.e a hosted solution rather than installing it on local machine to build this?

auekk2787
Forum|alt.badge.img+12
  • auekk2787
  • Brainy
  • November 14, 2025

Are there release notes for extensions? I see you can now select multiple tables!

nico_skor
Forum|alt.badge.img+1
  • nico_skor
  • New Participant
  • December 18, 2025

Hi! Another piece of feedback: it doesn’t look like the components listed in the documentation work. I tried to use the ConfirmationDialog one, and I gave up. The documentation has something like the below, but TypeScript throws an error saying the module does not have such an export. I tried importing from “@airtable/blocks/base/ui”. Typescrpt was happy with that, but Airtable throws an error when running the extension (Unexpected import when running block in interface). So I just added my own control. Not a big deal in this case but if I had to use controls such as RecordCard.

import { ConfirmationDialog } from "@airtable/blocks/ui";

 

Took a little bit to find, but there is a documentation page specifically just for the custom interfaces. It doesn’t seem to have all the same features as the regular extension api. 

https://airtable.com/developers/interface-extensions/api/models/Base

Forum|alt.badge.img+10
  • BenFortunato
  • Known Participant
  • December 31, 2025

I’m curious if the interface extension are also supported on mobile devices? 

Forum|alt.badge.img+18

After a lot of trial and error and help from Claude Code, I was able to create a custom interface extension that auto-completes an address that is being entered using Google Maps API. This is a huge win for my client, as the other options are MiniExtensions or Fillout Forms.  The Google Maps API key is saved in the Settings.
 

 

    abgates
    Forum|alt.badge.img
    • abgates
    • New Participant
    • May 11, 2026

    Hit FORBIDDEN: 'You can only run your development block in the original base where it was created' even when running a freshly initialized block from the CLI in a clean folder. Base appPNpzbWfCuJ1mef, fresh extension created via Builder Hub today. Both fresh block init and a copy of the official Hello World TS template produce the same error. CLI version 3.0.3. Org: Clearlink. Has anyone seen this?"

    TheTimeSavingCo
    Forum|alt.badge.img+32

    ​@abgates Hm, as a datapoint, I just tried this and it worked, using  @airtable/blocks-cli/3.0.1 darwin-x64 node-v24.9.0

    1. Created a new extension via https://airtable.com/create/extensions/new
    2. Ran `block init`, it downloaded and installed

    3. Ran `block run` and it started up

    4. In an Interface, added it to a Dashboard layout and clicked ‘Develop’ and that loaded up:

      1.  

    Adam, Airtable Consultant - https://thetimesaving.company
      abgates
      Forum|alt.badge.img
      • abgates
      • New Participant
      • May 12, 2026

      ​@TheTimeSavingCo  Update: figured it out! The .block/remote.json should have "baseId": "NONE" instead of the actual base ID. The CLI setup instructions for Builder Hub-created extensions show block init NONE/blkXXXXXXXXXXXXXX—that NONE/ is meant literally. Setting baseId to the actual base ID produces FORBIDDEN errors. Not sure where the mixup happened, but I am relieved to have finally figured it out. 

        Jack_Manuel
        Forum|alt.badge.img+18
        • Jack_Manuel
        • Brainy
        • May 20, 2026

        hi, ​@thelus - thanks for the excitement :) and for the post! to answer your questions:
         

        • re: adding to colorUtils , we’ll likely still return the rgb/hex codes. that said, we’re open to modifying the opts param or coming up with another solution that addresses this issue. I’ve added it to our backlog.
        • re: custom linked record views: we have adding support for allowing interface extensions / custom elements to be installed inside of record detail views on our roadmap. I believe once that support is shipped, we’d support your use case of being able to visualize your linked record data as you see fit

        hope this answers your questions, and do let me know if it doesn’t!

        - Duretti

        Hi, any update on custom linked record views in interfaces?

        kylevenberg
        Forum|alt.badge.img+3
        • kylevenberg
        • New Participant
        • July 13, 2026

        Hyperagent helped me build - I used this video to gather more context of how to set it up initially and get running - I’m all set up. Really great stuff! Appreciate the video!

        Forum|alt.badge.img
        • Dr_Mayer
        • New Participant
        • September 21, 2026

        Airtable Interface Map Rendering Issue – Mapbox runtime failure

        I’m writing to share a summary of an issue I’ve been investigating in our Airtable Interface extension as I’ve tried to replicate the interface map extension linked here: Airtable/interface-extensions-map. It appears that even a freshly cloned version of this repository will fail to render the background mapbox tiles. 

        In our investigations, we’ve confirmed that the Mapbox token and geocoding access are working as expected. Direct calls to the Mapbox style and geocoding endpoints both return HTTP 200 responses, and the app logic is not blocking the map from rendering. We also confirmed that the geocoding fetches are succeeding and the app is reaching the point where it attempts to initialize the map.

        Despite that, the map never renders in the deployed Airtable block. In the browser console we are seeing runtime errors from the bundled Mapbox code, including:

        • ReferenceError: vt is not defined
        • ReferenceError: Cannot access 'De' before initialization

        These errors occur during Mapbox tile/style initialization, before the map can finish loading. 

        We also ruled out several other likely explanations:

        • invalid or expired Mapbox token
        • missing Mapbox scopes
        • geocoding rate limiting or API failure
        • a configuration issue with custom properties
        • the app intentionally hiding the map while geocoding is still in progress

        At this point, sources I’ve consulted suggest an incompatibility between the Mapbox bundle and the Airtable block environment, rather than a problem in the geocoding or token setup.

        I’d appreciate any guidance or confirmation on whether this is a known compatibility issue, or if there are any recommended constraints around Mapbox library versions or bundle behavior for Airtable Interface Extensions.

        Thanks very much for your help.

        Best,
        Terin Mayer

        Terms & ConditionsAccessibility statement