Record a support request only after the customer confirms its details, then verify the saved record. This walkthrough uses Airtable record identity; the Google Sheets append workflow is an alternative when a controlled team log fits the job.
Before you begin
- Complete Airtable connection and guarded Workflow setup in a dedicated test project. The connected account needs read/write access to the intended base/table.
- Prepare a Requests table with
RequestKey,Name,Email,TopicandStatus, or map the example to the owner’s actual schema. - Have the application developer provide validated literal fields, a stable RequestKey and backend-recorded confirmation. Keep approval and identity out of model/browser control. The input builders validate this example’s values; they do not authenticate a login or record confirmation themselves.
Record the confirmed request
Collect and confirm only the required details
Ask for the request topic and contact details, then show the proposed request to the customer for confirmation. The backend validates the fields, records that confirmation for the current request and prepares one records array. A Trigger instruction asking the model to confirm is not an enforcement gate. Use the guarded Workflow; keep the raw create tool off other agent tool lists.
Provide the approved request
Studio
In More → Variables, check the approved-input variables, data_write_approved and the empty result variables from the manual. Have the developer populate the confirmed fields and stable key before the matching turn. In the Workflow’s Integration step, choose Airtable → Create records, then bind the fixed base/table and prepared records array through each input’s Default value.
Code
Call supportRequest on the backend with confirmed: true only after recorded approval. Use its airtableRecords as the provided JSON array. The guarded Workflow builder consumes approval before calling the Integration step and clears stale result variables. Create/attach/compile it using the Airtable manual’s Code instructions. Standalone airtable_create_records is a separate backend action and must check the same authorization/confirmation before execution.
Inspect the actual saved record
Capture records[0].id from the current native result; standalone results use output.data.records[0].id. Read that same record, compare RequestKey, Name, Email, Topic and Status, and retain the mapping in your application. Expose both data_action_outcome and data_action_id as actual instruction references, as shown in the provider manual. Only the current verified outcome after every submitted-field comparison may produce “Your request is recorded.” A created record is not a sent email or accepted human assignment.
Verify confirmation and retries
Run “Please record my account-access problem” through the application. Check missing details, an unconfirmed request, a confirmed request and rejected write access. Only the confirmed request may create one intended record and receive a success acknowledgement.
For a lost response or timeout, query the stable RequestKey and inspect any matching records before retrying. Airtable create and Google Sheets append can duplicate a request; neither is an idempotent upsert. If the outcome is uncertain, say so and reconcile it rather than automatically repeating the write.