I would MUCH rather have Ai focus on a small bit of information over handling large tasks. Here's a look at what that means (See Pictures) In this automation, we’re trying to create a clean "draw-request folder flow" (client specific language) in Google Drive for each draw against a Construction Loan, then link those exact folders back to Airtable so the team can go straight to the right draw, photos, and invoices. BUT, the problem is that historical loan folders are messy. Some loans already have a draw folder, some do not, some use names like `Draws` or `Draw Requests`, and some even have duplicates. We could hard-code a lot of matching logic, edge cases, and fallback rules, but that becomes brittle... fast. The AI step gives us a much simpler layer. The script just returns the loan subfolder list, very specific and narrowed down data. I don't want Ai digging into everything in Google Drive when a script can just do it QUICKLY. After we get the subfolder list (See Dark Photo), AI interprets that list: - Does a draw-related folder exist? - Are there multiple, and which existing one should be treated as the oldest valid candidate? - That gives the next Google Drive script a clean decision input instead of forcing all that fuzzy logic into code. The win is that the rest of the automation stays deterministic! Scripts do the heavy lifting, AI handles the naming ambiguity, and the folder-creation step can reliably decide whether to reuse a folder or create a new one without a giant pile of special-case code. I KNOW this is a little advanced, but hopefully this opens up the sandbox for you a little!

UPDATE: There is a related follow-up task to this post here; 'Two-step record creation process?'. But as I articulated the follow-up task it slowly dawned on me I may have got the solution to what I'm asking below! ##Original post I'm adding a range of targeted forms to my website with a view to using webhooks to add new records to a range of tables. I'm using ConvertBox as my form tool (lets me split test different forms) and though I've used webhooks with ConvertBox before, I've only used them to trigger a Make scenario. But for this use case, I don't need a scenario to fire. I just need the form inputs passed to my corresponding tables. So wondering what I need to do make that happen. PS. By way of a backup I know I can fire a Make scenario to create a record so feeling like I already have my plan B if no quick and easy Plan A option exists?

This is effectively a follow-up task to my previous post; 'Can I use webhooks to create new records directly into Airtable?' I know the easiest way to create a new record would be to create an Airtable form. But I prefer to use ConvertBox due to it's simplicity and it's ability to split-test form variations. The only problem in this use case, is it would be nice to have a user submit one or more images at the time they complete the form. But ConvertBox doesn't facilitate uploads. However, it does facilitate multi-step forms. And I see I can embed an Airtable form into a ConvertBox step. So that does give me some options. So my question is if a user submits all the text-based information in the first step, how do I make sure the record is created so that the optional image upload step that follows is attached to the newly created record. Mmmm... I think that just writing this post out, I've realised the 'text' form I created in ConvertBox could be redundant if I just embed the Airtable form instead. That way the image field is there right at the time of record creation! PS. I'm leaving this post up as I know the community is always discovering new and interesting ways to use Airtable and this might be of value to someone else one day! PPS. I'll report back on whether my epiphany comes to pass and I nicely marry up ConvertBox and Airtable. If so, that will be a huge win. (And as I think out loud, it also provides a solution to my previous post!).

I didn't say this out loud when I was recording the video, but as I thought more, the question became: "How to automatically remove ONE multi-select tag without removing all the other multi-selected tags?" PS. My interim solution will be to separate the Status and the Tag relationship for that tag. I'll simply remove the automation update that extends the array with the 'Auto Exclude' tag. In other words, the status can change and the tag (I want removed in the video example) won't even be applied in the first place. On reflection this may be a more appropriate solution. My question then loses it's priority business need and becomes more of a curiosity-based "I wonder how you do that" question.

If you’ve ever wanted to group an entire Airtable table together, but had nothing in common across the records to group by, here’s a simple trick. Airtable only lets you group when records share a value. So if every record is different, grouping by something like Item Name won’t help much. What I do instead is create a checkbox field called Grouper or All Grouper, fill it in for every record, and then group by that field. Now the whole table sits inside one grouped section, which is useful when you want a quick high-level view of everything at once. It’s especially helpful if you want to see rollups, totals, or summary information at the top without creating another table just to get that one view. https://www.loom.com/share/a5a0ef8c8ac34fd59fb3ef878df7f815