Build with

Change an existing support request while preserving its identity, then read back the saved value. This walkthrough uses Airtable’s record ID. For a spreadsheet, follow Updating existing cells and account for moving rows and concurrent edits.

Before you begin

  • Complete the Airtable manual, including its guarded Workflow and approved input variables.
  • Have a backend mapping from the authenticated customer/request to the intended Airtable base, table and record ID. The customer’s display name, email or row number is not the record ID or proof of access.
  • Agree which fields/status values the customer may change. The example changes Status to Closed; it is an illustrative business policy, not a built-in permission rule.

Apply the confirmed change

1

Resolve the authorized request

Authenticate the application customer and authorize the request-to-record mapping on the backend. Read the current record and check its identity/status before offering a change. Stop for missing or ambiguous mappings; do not ask the model to search for another customer’s record.

2

Confirm the permitted field change

Show the intended request and proposed status, then have the backend record confirmation and call recordChange in the input builders. It requires a confirmed authorized record ID and the example’s allowed status. Omit unrelated fields so the operation does not unintentionally change them.

3

Run the guarded update

Studio

In the guarded Workflow, choose Airtable → Update records. Provide the fixed base/table and the backend-prepared records array; do not expose raw update inputs as a Global tool. Keep the approval Condition before the Integration step. Clear the result at entry and consume approval before writing so a repeated invocation cannot reuse it.

Code

Use the same guarded graph with the discovered airtable_update_records tool ID and the current action inputs. Supply only the backend-authorized {id, fields} array. Set its readback to airtable_get_record for the same ID and compare the returned RequestKey and Status with the approved values. Create, attach and compile as described in the manual; a standalone call is not an agent attachment.

4

Read back before acknowledging

Require the current update’s matching records[0].id, then use Get record for that same ID. Compare the saved RequestKey and Status: Closed with the approved request. Expose the current data_action_outcome and data_action_id through actual instruction references. Only verified after a matching readback may produce the success answer; an ID alone is insufficient. If the write or readback fails, keep the outcome unverified and investigate before retrying.

Verify identity and saved effect

Test the change through the authenticated application, then test another customer’s ID, missing confirmation, a disallowed status, revoked access and an uncertain response. Inspect the actual Workflow invocation, inputs, current result and saved record. Private identity and approval must be rebuilt by the backend on every turn; model guidance alone cannot enforce them.

Airtable record identity avoids spreadsheet row movement, but a read followed by an update is still not a compare-and-set transaction. Define who may update the request concurrently and how to reconcile conflicting business changes.

Use the up and down arrow keys to select a result, Enter to open it, and Escape to close the search.