Salut @Hadrien_Vuillet-A-Ci, the use case you’re describing sounds fairly straightforward.
Based on the info you shared, an automation is ostensibly the best way to go about this, both in terms of near-term benefits and beyond. Although tying a recurring automation to a form that you still need to fill out manually is probably not the best approach here, even though it would still alleviate the inconvenience of your current workflow.
But assuming your monthly appointments are in the hundreds, or even low thousands, the $20 Pro plan comes with more than enough computing resources to have a base that updates in real-time with minimal involvement on your end.
This kind of undertaking is definitely within reach of any moderately motivated individual; Alexey already outlined how you could achieve it without so much as glancing at any actual code. But your first instinct was correct: JavaScript is, generally speaking, the best tool for the vast majority of Airtable-powered and -adjacent development.
While your circumstances naturally aren’t as favorable if you’re just starting out, coding custom behaviors tends to be faster than describing complex logic via blocks and web forms. And its results tend to be easier to both maintain and scale. Dareisay this seems like a great project for a JS newcomer due to its narrow scope.
That said, I’m guessing most healthcare professionals can think of better ways to spend their sparse downtime. If you’re one of them, the good news is that you woon’t have any trouble commissioning someone who’s willing and able to handle this quickly and affordably. You could try posting on the Hire a Consultant board or contact someone via the recently launched Airtable Consultant Directory. Feel free to DM me for a quote, as well.
P.S. In case you do decide to tackle this yourself, returning to these boards with detailed questions about any technical difficulties you encounter is a great way to fast-track the learning process with minimal frustrations. That, and reading Airtable’s super-comprehensive documentation.
