Hey there, ​@BethHanson! Thanks for submitting such a great question! Because your question hasn't yet received an answer/solution from the Community, we've created a Support Case on your behalf with our Airtable Expert Team to get you the quickest response possible. Please check your email for follow-up and your case reference number—and continue to follow this thread as new community members tend to share answers and add knowledgeable responses regularly. Thanks!

Hey ​@BethHanson!

Absolutely. This can be achieved. If I may, I would actually suggest to have all of your bases merged into one unique base unless you have great reasons for not doing that (e.g. hitting record count limit, or disclosure of information to different users).

To handle automations between DIFFERENT bases (e.g. when automation in base A gets triggered, create a task in base you’ll need to either (a) use scripts within your automation of base A to create a record in base B via API call, or (b) have your automation in base A call a webhook (probably via script as well, but way shorter and easier to handle) to trigger an automation in a third party automation tool such as Zapier, Make, or n8n (more about them on this other Article), and have the workflow/automation on this tool create the record on base B. 

I would say option (b) above is pretty much “no-code” so no technical background is needed.

If you need any help setting this up, please feel free to schedule a call using this link!

Mike, Consultant @ Automatic Nation

Hmm, if you’re on the Business plan you could try using the ‘When email received’ trigger?  On a Teams plan you could use the ‘When Outlook email’ received trigger too.  Wouldn’t be as clean as using a third party tool like Mike suggested though

If you’re interested in dabbling in code stuff, you can look into Airtable’s webhook automation trigger to create the records in your task base too; fairly straightforward and simple script