Use miniExtensions to copy reviewed values between fields in the same Airtable record, but decide what a blank proposal means before running the automation. An empty source is not an instruction to erase the destination. A reliable workflow separates replacement values, review decisions and any explicit removal request.
This tutorial uses a small internal service catalog. An editor proposes a revised description and website for a service entry. A reviewer approves the wording before it becomes the current catalog data. The example starts with one fictional record and a manual run, not an unattended publishing system.
Build a staging area beside the current values
In a Catalog table, create Service Reference (single line text), Current Description (long text), Proposed Description (long text), Current Website (URL), Proposed Website (URL), Review State (single select), Applied On (date) and Reviewer Notes (long text). Use Review State choices Draft, Ready to Apply, Applied and Needs Clarification.
For sample CAT-01, set Current Description to “Introductory workshop” and Proposed Description to “Half-day introductory workshop.” Give the current and proposed website fields distinct, harmless example URLs that you can recognize. Keep the sample out of any public-facing selection while testing.
These are suggested fields, not a built-in approval system. The moderation workaround describes separate current and proposed fields. The reviewer, not a successful copy operation, decides whether a proposal is appropriate.
Configure two explicit field pairs
Create Copy Airtable Value to Another Field in the intended workspace and base using the automation creation steps. Select Catalog as the working table.
Follow the field mapping guide. In Fields to Copy, select Proposed Description first and Proposed Website second. In Destination Fields, select Current Description first and Current Website second. Matching positions determine the pairs.
Use equal-length lists, writable destinations and compatible field types. A field cannot be both a source and destination in this configuration. Read the two lists together before running: the example should map description to description and website to website, not merely contain four plausible field names.
Keep the configuration small enough to inspect. If more field pairs are added later, treat the mapping as a changed operation and repeat the sample checks. Do not assume that a previously successful two-field setup validates every future mapping.
Limit the first run to one approved sample
Create an Airtable view named Approved Copy Sample containing only CAT-01 with Review State set to Ready to Apply. Use the automation’s Filtering control to select that view, following the filtering instructions. Open it and confirm the actual row before continuing.
Because both current fields already contain values, inspect Existing Data Handling. The overwrite guide places Overwrite under Processing Behavior. Enable it only after reviewing the proposed replacements and selected scope.
Before running, keep an appropriate recoverable record of the original sample values. Then use the manual Run controls and inspect both destinations. Check the literal values in Airtable, not just whether the run has finished. The expected outcome is the two intended replacements on CAT-01 and no changes to records outside the selected view.
Test the blank case separately
Reset the sample’s current fields to known values. Leave Proposed Description blank and put a recognizable replacement in Proposed Website. Inspect the mapping and selected sample view again before a second run.
The documented blank behavior means the description pair is skipped rather than cleared. The website can still be the intended nonempty replacement. Inspect both fields afterward.
For a checkbox pair, the documented caution is especially important: an unchecked source does not uncheck an existing destination. Do not use a checkbox copy as a general “make these fields identical” operation without accounting for that difference.
If the editor wants the current website removed, capture a distinct removal request and have an authorized reviewer carry it out through a separate, checked process. Do not encode removal by leaving Proposed Website blank or by inserting a placeholder that could accidentally become public data.
Prevent an old approval from applying a new proposal
A Ready to Apply label must refer to the exact values the reviewer saw. Before processing a real batch, stop editing of those proposals through the relevant workflow or agree on a controlled editing window. Check that no contributor can change a proposal while retaining an earlier approval.
After verifying the copied values, staff sets Review State to Applied and records Applied On. The two configured field pairs leave those review fields unchanged. An Applied label should reflect a checked result, not merely that someone clicked Run.
For a later revision, create a new review cycle and reset the approval state before accepting new proposed content. Preserve any history your organization needs before reusing staging fields. A pair of current and proposed columns alone is not an immutable audit trail.
Expand only after the checks are understandable
Repeat the sample with two different records and include an unapproved record outside the processing view. Confirm mapping, overwrite behavior, blank handling and scope.
Once the behavior is clear, use a carefully reviewed view for the intended batch. Scheduling is optional and requires its own approval-state and edit-control design. The copy automation is useful for applying known nonempty replacements; it does not verify the quality of the content, authorize changes or decide when something should be published.
The practical stopping point is simple: each destination contains the intended value, skipped blanks are understood and the reviewer can explain what changed. Only then should the team mark the batch applied.

