It's worth touching on Airtable's data model.įrom a developer's perspective, Airtable is basically a hosted database fused to an easy interface for creating and managing data. When building in Airtable, you will face a couple constraints when working with 3rd party APIs, caching data, or manipulating the UI. Lastly, as your considering whether to build in or on Airtable, consider the functionality you need. The new name is slowly catching on but you'll still see the term blocks pop up here and there. Note: Airtable Apps were formerly known as Airtable Blocks.
#AIRTABLE API SKD PRO#
Meanwhile, scripts and custom apps are only available on pro and enterprise plans. Automations are available on every plan, but capped at different limits. The REST API is available on every plan to every Airtable user. In these use cases, you'll be using the Airtable REST API directly or using a tool like the one I helped build - Sequin.Īs you decide whether to build in on on Airtable, you should consider what Airtable plan your users are on as well. This might be a custom internal tool, a dashboard built in Google Data Studio, a public Next.js website, or inside another SaaS application all together. If you are building on Airtable, then you are building for users outside of Airtable. But by and large, the end user is in Airtable. Note: Yes, I know, automations can trigger actions outside of Airtable. For any code you want to run in Airtable you'll be using either scripts, automations, or the custom app SDK.
#AIRTABLE API SKD SOFTWARE#
When you are building in Airtable, the user is logged into Airtable and using your software within the Airtable interface.
in Airtable) or outside Airtable in another app or tool (i.e. Who is your user and what do they need? This age-old question is still the first one to ask as you begin to consider which Airtable developer tools to use.Īt a high-level, you can classify Airtable's suite of developer tools as either supporting use cases that happen inside the Airtable interface (i.e.
0 kommentar(er)
