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!).

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?

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.

Real business application here! Create beautiful emails directly from Airtable with the power of HTML. (Cheat with Ai if you don't know HTML or any coding) This DOES need you to use the Script block in the automations. SO, I created this as a simple getting started with scripting in Airtable walkthrough. There are a few key things to hone in on in here: - How to get information INTO the script so that the script can manipulate or use it. - How to get information out of the script so it can be used for the following automation steps. During this whole video I tried to give you my best practice tips and go over some common gotchas that might happen, especially when you're working with AI to help build out these workflows! - 00:00 Why scripting matters in Airtable - 00:24 The business use case: sending supplier emails - 01:05 Breaking down the script inputs and structure - 03:13 Passing data from the script to the next automation step - 04:08 Rebuilding the automation from scratch - 06:10 Setting up inputs, table IDs, and field references - 12:21 Building the email output - 16:06 Adding error handling and success checks - 19:26 Why this matters for real business workflows - Did this unlock anything for your Airtable workflows? - Was anything confusing about this? - Do you have any further questions about how to use scripting automations?

Part 4 of "From Spreadsheet To Airtable" I’m moving into the purchase tracker in this one and starting to tighten up how purchase data should actually work inside the base. This is where the system starts becoming more usable because the fields, IDs, linked records, and cost calculations begin working together in a more intentional way. → Part 4 - Cleaning Up The Purchase Tracker In this one, you’ll see: - how I set up a PO numbering system with formulas and auto numbers - where auto numbers are helpful and where they can get a little tricky - how I connect suppliers and inventory into the purchase tracker - when I would use linked records versus when I might want hard-coded historical data - how I think through total cost calculations and naming things more clearly A big part of this one is seeing how small setup decisions can affect everything that comes after, especially when you are working across related tables. If you watch it, what stood out to you most? Any tips you’ve learned around purchase tracking, naming conventions, or deciding between dynamic fields and historical records?