Skip to main content
Solved

Want to use an automation to create a record in one base when a specific condition is met in another base

  • November 7, 2025
  • 7 replies
  • 44 views

Forum|alt.badge.img+2
  • New Participant
  • 2 replies

I have two separate bases. When a form is submitted in base1, a record is created. When a specific record matches a condition, i want to use an automation to create a record in base2.

Ive tried using the sync feature in the data layer, which appears to pull base2 data layer into base1 data layer but when i go to the automation, the table I want to create a new record in is there, but is greyed out and cant be selected. I went through permissions with someone from airtable, but we still can’t figure out what the issue is.

 

This is from the automation

In the table field i can see the table i want to create a new record in, but it is not selectable. IN the data layer, it is listed as grid view

 

 

 

Best answer by ScottWorld

Destination sync tables are read-only, so you can’t add records to them.

However, is there a specific reason that you have 2 different bases? That is almost never the recommended setup for a database system, so it sounds like your setup may be incorrect.

- ScottWorld, Expert Airtable Consultant 

7 replies

ScottWorld
Forum|alt.badge.img+35
  • Genius
  • 9787 replies
  • Answer
  • November 7, 2025

Destination sync tables are read-only, so you can’t add records to them.

However, is there a specific reason that you have 2 different bases? That is almost never the recommended setup for a database system, so it sounds like your setup may be incorrect.

- ScottWorld, Expert Airtable Consultant 


TheTimeSavingCo
Forum|alt.badge.img+31

Try creating a sync of the table from Base1 in Base2 instead?  You can then create an automation that’ll trigger when a new record gets created in the synced table, and its action will be to create a new record in the appropriate table in Base2


 

 


Mike_AutomaticN
Forum|alt.badge.img+28

Hey ​@MRC228,

As mentioned above you would need to come up with a clunky workaround to make this work natively within Airtable. An alternative solution you might want to explore is to set up your own automation in n8n or similar automation tool.

In this way:
1. Record A meets cettain conditions in Base A
2. Airtable automation gets triggered in Base A
3. Airtable automation makes a webhook call to n8n
4. n8n receives such webhook call, gets data from Record A in Base A
5. n8n automation creates record in Base B.

This should be really simple to set up. If you need any help, feel free to grab a slot!

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

Mike, Consultant @ Automatic Nation 
YouTube Channel


Forum|alt.badge.img+2
  • Author
  • New Participant
  • 2 replies
  • November 7, 2025

Destination sync tables are read-only, so you can’t add records to them.

However, is there a specific reason that you have 2 different bases? That is almost never the recommended setup for a database system, so it sounds like your setup may be incorrect.

- ScottWorld, Expert Airtable Consultant 

Thank you Scott. This is what i was afraid of. I took the time last night to recreate everything in a single base and it’s working beautifully now.


Forum|alt.badge.img+2
  • Author
  • New Participant
  • 2 replies
  • November 7, 2025

Try creating a sync of the table from Base1 in Base2 instead?  You can then create an automation that’ll trigger when a new record gets created in the synced table, and its action will be to create a new record in the appropriate table in Base2


 

 

I tried it both ways but was never able to get it to work. I recreated the “new” base interfaces and forms in the larger existing base and now everything is working


ScottWorld
Forum|alt.badge.img+35
  • Genius
  • 9787 replies
  • November 7, 2025

@MRC228 

That’s great to hear that you’ve got everything working beautifully now by combining everything into one base! :)

If you ever need to hire the best Airtable consultant to help you with anything else that is Airtable-related, please feel free to contact me through my website: Airtable consultant — ScottWorld


TheTimeSavingCo
Forum|alt.badge.img+31

I tried it both ways but was never able to get it to work. I recreated the “new” base interfaces and forms in the larger existing base and now everything is working

Hm yeah that’s weird, I’ve got this set up in a couple of bases and it works fine.  Still, sounds like you solved your problem!