> ## Documentation Index
> Fetch the complete documentation index at: https://filla.io/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Update fields on submit

> Automatically write values to record fields after a form is submitted.

## What this does

The **Update submitted record** action automatically fills in fields on the Airtable record that was just created or updated by the form submission. You define which fields to update and what values to write.

This is useful for:

* Setting a status field to "Submitted" after every submission
* Writing a timestamp using `@{Submission Date}`
* Calculating and writing a derived value based on submitted fields
* Setting a hidden "source" field to a fixed value

## Setting up the action

<Steps>
  <Step title="Open the Automations tab">
    In the form editor, click the **Automations** tab.
  </Step>

  <Step title="Create or open an automation">
    Create a new automation or open an existing one.
  </Step>

  <Step title="Add an action">
    Click **Add action** and select **Update submitted record**.
  </Step>

  <Step title="Add field updates">
    Click **Add field update**. Select the field to update and enter the value to write.
  </Step>
</Steps>

## Field update settings

Each field update entry has:

| Part      | Description                                                                              |
| --------- | ---------------------------------------------------------------------------------------- |
| **Field** | Which Airtable field to update on the record                                             |
| **Value** | The value to write. Supports variable text. Type `@` to reference submitted form fields. |

You can add as many field updates as needed. All updates in one action are applied together in a single write to Airtable.

## Using variables in values

The value field supports `@` variable references. This lets you:

* Write the respondent's submitted answer to a different field: `@{Email}`
* Combine values: `@{First Name} @{Last Name}`
* Reference computed values: `@{Submission Date}`

**Example:** After submission, set a field called "Full name" to `@{First Name} @{Last Name}` where both are separate fields on the form.

## Conditional execution

Each action can have an optional **"Only run if..."** condition. When set, the Update action only runs when the condition is true.

**Example:** Only update the "Priority" field to "High" when the "Budget" field is greater than 10000.

## Order of execution

Actions within a single automation run in sequence. If you have a Wait action before the Update action, the update happens after the delay.

## Common questions

<AccordionGroup>
  <Accordion title="Can I update fields that aren't on the form?">
    Yes. The Update submitted record action can write to any field in the connected table, not just the fields the respondent filled in. This is one of the most useful aspects of this action.
  </Accordion>

  <Accordion title="Does the update overwrite what the respondent submitted?">
    Yes, if you target the same field. Be careful not to accidentally overwrite a field the respondent filled in unless that's intentional.
  </Accordion>

  <Accordion title="Can I use formulas or calculations in the value?">
    The value uses variable text. You can reference submitted fields and combine them, but not compute mathematical operations directly. For calculated values, use an Airtable formula field and trigger a value based on that, or handle calculations in a webhook.
  </Accordion>

  <Accordion title="When does the update run relative to the respondent seeing the thank you page?">
    The update runs after the record is saved to Airtable, which happens before the thank you page is shown to the respondent. However, automations run asynchronously, so the thank you page may appear a moment before the update is applied.
  </Accordion>
</AccordionGroup>