Create Records based on data in a different table

Hey ​@DenS,

Would you mind sharing some more details on the exact workflow?
E.g. what are you doing or should be doing, and what should be happening?

My undertanding is that you are creating a new interview record as Step 1?
What are next steps? Topics and Posts should be created automatically based on what logic/criteria?

Completely different matter, but would love to have you join our Airtable Hackathon! Make sure to sign up!!

Mike, Consultant @ Automatic Nation 
YouTube Channel  

Check if the AI fields are set to auto-run at creation.

Or run a workflow in Make and use that to put data back in other tables.

Could you provide some screenshots of the tables and the automation in question that isn’t working like you want?  If you could private message me a link to your base I could take a look for you too!

Hi everyone,

I’ve created an app with Omni by the prompt:

Create an application to analyze sociologists interview about nation values and features. It should have three datasets: Interviews (with columns: Title, Date, Interviewee Name, Audio, Transcript, Summary of Interview, Topics, Posts), Topics (with columns: Name, Description, Suggested Post Ideas), Posts (with columns: Content, Summary, Suggested Hashtags). User will add an interview audio file, AI should make the transcription and summary, extract discussed topics and suggest social media posts, based on the topics. Fullfill datasets with two examples.

 The app with 5 samples was created. But when I add a new interview neither topics or posts are being created. 
 

As others have mentioned, have you checked that the AI fields are set to auto run? Screenshot below is an AI field, it’s not set to autorun in this instance, you have to manual run it by clicking the refresh icon (circled in red). 

Hey ​@DenS , DMed you!

Love the concept!

• We don’t have a native way to transcribe audio to text, that will have to be done external to Airtable
• This could potentially be done on one table, which would reduce complexity greatly since you will need some tricks to generate entirely new records for Topics and Posts off of the Interviews table. 

As others have mentioned, have you checked that the AI fields are set to auto run? Screenshot below is an AI field, it’s not set to autorun in this instance, you have to manual run it by clicking the refresh icon (circled in red). 

 

Hello, thanks for your recommendation, but I think there is an another reason. Interviews, Topics and Posts are placed on different tables.

The question is how to force AI to generate new instances in the different tables when new interview appear?

Maybe it can be solved with new Automation?

Hi Alex!
The concept appeared inspired by your case that was showed in “Build your first AI app with Omni and Field Agents”. The process of podcasts analysing, topic extraction, and posts creation was demonstrated there. Unfortunately I have no record of the meeting, could you send the link to me I would try to figure out how it was made there.

Thanks for the screenshots!  

Try creating an automation that triggers whenever the Transcripts field has been fully filled in.  This could be a checkbox field if you’re typing / pasting the data in or something

The automation would then take the text from the Transcripts field and we’d use a ‘Generate text with AI’ step, followed by a ‘Run a Script’ step and a Repeating List, and your end automation would look something like this:

I’ve set it up here for you to check out and made a step by step guide as well:

In the following gif, the automation extracts the hobbies from the ‘Notes' field and then creates one record per hobby in the ‘Hobbies’ table and links it back to the triggering record

​@TheTimeSavingCo As always brilliant but just as an academic question here, instead of scripting couldn’t you use the AI Generate Structured Data action? It’s probably overboard as your script is so simple, just considering it as an alternative. 

​@DisraeliGears01 Ohh, you’re right, using Generate Structured Data makes way more sense here; I’m going to update the guide to use it instead

Thanks for pointing this out!  I defaulted to scripting out of habit sigh