I’m surprised I am the first to reference this comprehensive and noteworthy effort by the folks over at Sync Inc.
But even more impressive - the authors entirely resisted plugging their own SQL technology until a very brief mention of it at the end of this very lengthy and detailed blog post - true professionals who value and appreciate content over cash.
Take a read - you’ll probably bookmark this and use it as a reference until they make it into a book. :winking_face:
This is a very nice piece of writing. Not only is this a great introduction to to people who are already developers, the beginning is great for those who are new to writing code or are thinking of hiring someone else to write code.
Our goal is to make The Complete Developer’s Guide to Airtable the up to date, reliable resource we wish we had when we started building on Airtable. So as Airtable release new tools, we’ll add tutorials and details to the guide.
In this first update to the guide, we’re coving Airtable’s new incoming webhooks for automations:
Next up on our list is to dig into Remote fetch in Scripting App. DM me if there is a topic you’d like us to cover.
Thanks so much for updating that, @Eric_Goldman! :grinning_face_with_big_eyes: :raised_hands:
And many thanks to YOU for helping us all learn how to use Airtable better!! Your contributions to the community are fantastic & amazing! :slightly_smiling_face:
In the second major update to the developer’s guide to Airtable, we’re covering Airtable’s new interfaces:
In this section of the guide, we dissect Airtable interfaces. When should you reach for an interface versus a script, custom app, or prebuilt app? How do they work?
Then, we show a practical example - you’ll see how to build an interface to help a sales team keep an Airtable CRM up to date.
With the guide, we want to help technical teams and developers understand their options and the practical build experience when working with different Airtable dev tools. We hope you find it helpful.
As always, thanks to this amazing community for uncovering all sorts of interface nuances, which we tried to compile into the guide :raised_hands: