How to retain mapped fields when establishing new Airtable connections

Hi Community,

After importing a previously saved scenario (blueprint), is there a way to preserve all the mapped fields in my Airtable modules when connecting the Airtable module to a new base that is a duplicate of the original Airtable base connected to the initial scenario?

To elaborate, I've developed a content publishing tool intended for sale to clients. This tool comprises an Airtable base (which I duplicate in the client's Airtable environment) and several callin.io scenarios that manage the automations supporting the Airtable base.

The challenge I'm encountering is that when I attempt to set up my callin.io blueprints in a client's environment, I lose all the mapping in my Airtable modules. This occurs even though the database structure is identical, the field names are the same, and I'm not using "column ID" for field identification.

Essentially, upon connecting the Airtable module to a new base, it discards ALL the stored information. Is this something that can be retained if I utilize the callin.io.com team templates system?

Example of a module with complete mapping BEFORE updating to the new Airtable base:

image973×1897 134 KB

Example of the same module AFTER updating to the new Airtable base (All mappings are lost!!):

image886×1902 120 KB

This issue is critically important for my business, as I plan to offer these setups as Workspaces for clients to use in their own environments. It's not feasible for me to remap the entire scenario for every setup due to the numerous small mapping details involved.

Your assistance would be greatly appreciated.

Alex