This is possible with automations, but is there a specific reason for why you want to do this? Most people who think they want this actually just need to create separate views in a single Airtable table.

Because I am used to creating a master table with detail table. Where the customer has a table and the and the customer has a detail table.

I wouldn’t recommend that approach. That’s precisely what views and interfaces are for.

You can also expand a record to get an instant detailed view.

Yes this is a pretty simple automation but with a flaw

Trigger on new record created

Action - create new record with using fields from the original record to complete the fields from the other - however

Be careful as doing this may trigger the auto,action before you are finished adding data to the new record

So choices are - to have a field day a tick box to mark the completion of the new record creation or to complete these by for, or to change the trigger to be about going into a view

Or

Maybe better sync record to a new table and only sync the fields you want to use.

This last option is something we use to manage specific projects with records where there may need to be a project specific base.