Interface element: Button

• Record review

• Record detail

• List

• Gallery

• Grid

• Kanban

• Calendar

• Timeline

• Swimlanes

Note

Buttons are also available in blank layouts. However, blank layouts offer a legacy interface experience that requires different setup steps covered in this section. Additionally, many newer button features are unsupported in blank layouts. For that reason, we recommend using the layouts listed above.

Note

Overview layout types do not support buttons since that layout type is designed to orient and redirect end users with links to other interface pages or external resources.

The section below covers the basics about each button action type. For a more in-depth breakdown of setting up each action type, consult the information available here.

All interface layout types:

• Go to interface page - This allows you to add a convenient button that links to another interface page in this interface. You can also choose whether or not to force the browser to open that interface page in a new browser tab.

• Go to external URL - Add a link to another website, another interface, an Airtable base, and more. You can also choose whether or not to force the browser to open that interface page in a new browser tab.

All interface layout types except record detail or dashboard:

• Open record creation form - This button action allows end users to open up a form to add a new record.

Only record detail / record review layouts:

Note

Record review layouts include a record detail page as part of the interface you can configure, so these button actions are available in the individual record detail portion of that layout type.

• Update record - Configure a button to perform single or multiple updates to a record. One example would be to quickly update a record's status with the click of a button. You can also set the button to automatically move to the next record once it is clicked.

• Copy link to record - This button will allow end users to quickly copy the interface URL of the specific record that is currently opened in the detailed view that the end user has open.

• Delete record - A button to quickly delete a record opened from the chosen source. As always, users can press CMD Z to quickly undo an accidental deletion. Editors and creators with access to the underlying base can also access the base trash to restore deleted records.

• Apply record template - This button type will apply a record template to an existing record, saving end users time when they need to add certain preconfigured information to a record. Applying a record template will populate template values into any empty fields and append template values into multi-value fields, such as multiple select fields. Note that clicking this button will not create a new record and it will not overwrite any existing values on the record.

• Go to URL in record - This button action will open a URL that is stored in a field/cell in the current record that is opened. We recommend connecting this button action to a field specifically configured as a URL field type, though other field types such as single line text or formula can also be leveraged.

• Run automation - This button action will trigger an automation to run that is connected from the underlying base.

1. Open up a base in Airtable and click the Interfaces button at the top.

2. You may need to click the Pages option in the upper left portion of the interface editor screen. Click the page where you want to add a button. Remember, that certain button actions are only supported in record review or record detail pages.

3. Now, in the configuration sidebar on the right side of the page, scroll down to the “User actions” section and find the “Buttons” option. Click the cogwheel icon to configure a new button.

4. Click the + Add button action option.

5. Next, configure the button properties by clicking the box and arrow icon.

6. Next, move on to configuring the button based on the type of button action you chose.

1. Once you’ve reach the button configuration properties, give the button a descriptive “Label” so that end users know what the button does.

2. Under the Action section, optionally require confirmation. Learn more about configuring button confirmation here. You can also change the “Action” to another available button action type if needed.

3. In the Data section, there are two settings to configure:

   1. Choose the “Page” that end users will access when this button is clicked. Note that end users will only be able to access interface pages that have been shared with them. Additionally, you can only choose interface pages that are associated with the underlying base that you are working out of. If you are looking to send users to an interface page associated with another base, then use the “Go to external URL” button action instead.

   2. Toggle on the “Open in new tab” option to force the interface page to open in a new tab rather than load the page on the current tab. By default, this option is toggled on, but there may be use cases where you want this option off.

1. Once you’ve reach the button configuration properties, give the button a descriptive “Label” so that end users know what the button does.

2. Under the Action section, optionally require confirmation. Learn more about configuring button confirmation here. You can also change the “Action” to another available button action type if needed.

3. In the Data section, there are two settings to configure:

   1. Choose the URL “Destination” that end users will access when this button is clicked. We always recommend inserting URLs with the https:// prefix here.

   2. Toggle on the “Open in new tab” option to force the interface page to open in a new tab rather than load the page on the current tab. By default, this option is toggled on, but there may be use cases where you want this option off.

Note

This button will open a form that can create a new record in the table associated with this interface’s underlying table.

1. Once you’ve reach the button configuration properties, give the button a descriptive “Label” so that end users know what the button does.

2. In the Data section, there are two settings to configure:

   1. Source - This is the table where the record will be created. Note that only tables in the underlying base are available to choose from. Click the dropdown menu to select the table of your choice.

   2. Form - Click Edit form if a form has previously been connected to this button that you want to adjust, otherwise, click the dropdown here to open up a modal where you can:

      1. Choose an existing form layout configured in the past (You’ll also see how many times a form layout has been used i.e. how many times the form appears on other pages that are part of the interface you are editing.)

      2. Create a new layout

      3. Duplicate an existing layout

      4. Duplicate to form builder
         

         

Note

This button action can only update records associated with the table source connected to the record detail page where you are adding this button.

1. Once you’ve reach the button configuration properties, give the button a descriptive “Label” so that end users know what the button does.

2. Under the Action section, optionally require confirmation. Learn more about configuring button confirmation here. You can also change the “Action” to another available button action type if needed.

3. In the Data section, there are three settings to consider:

   1. Record source - Not configurable. The source is connected to the underlying base table connected to this interface page.

   2. Update record - Here you will set one or more actions (updates) to have the button perform when it is clicked. Click the cogwheel icon and then click + Add action to “Set” a field to be updated. Then, insert the value that the field will be updated with when the button is clicked. Note that this will overwrite, not append, any current value(s) in the field. Click the trash icon to delete a previously configured action.

      

   3. After update, move to next record - Toggle this on to move the end user to the next record on their screen after the button has been clicked and the record update has been made.

4. Next, set up the Appearance of the button. This includes setting a “Color before” and a “Color after” the button is clicked. You can also customize the button to change the “Label after” the button is clicked. Then, choose whether to “Show check icon” next to a record that has been updated. Note, that records that already match the update conditions set up in the “Data” section will appear as complete.

5. Lastly, configure “Visibility” Rules for the button. Here, you can click the cogwheel icon to set filtering conditions based on your use case’s individual needs. One common use case is to only allow certain users to see this button. Another example would be to only show this button for records associated with a particular status or category.

1. Once you’ve reach the button configuration properties, give the button a descriptive “Label” so that end users know what the button does.

2. Under the Action section, optionally require confirmation. Learn more about configuring button confirmation here. You can also change the “Action” to another available button action type if needed.

3. Next, you can change the Appearance of the button to be another color. By default, Airtable sets this color to be grey.

4. Lastly, configure “Visibility” Rules for the button. Here, you can click the cogwheel icon to set filtering conditions based on your use case’s individual needs. One common use case is to only allow certain users to see this button. Another example would be to only show this button for records associated with a particular status or category.

1. Once you’ve reach the button configuration properties, give the button a descriptive “Label” so that end users know what the button does.

2. Under the Action section, the “Require confirmation” setting will always be turned on in order to prevent accidental data deletion. Learn more about configuring button confirmation here. You can also change the “Action” to another available button action type if needed.

3. Next, you can change the Appearance of the button to be another color. By default, Airtable sets this color to be red.

4. Lastly, configure “Visibility” Rules for the button. Here, you can click the cogwheel icon to set filtering conditions based on your use case’s individual needs. One common use case is to only allow certain users to see this button. Another example would be to only show this button for records associated with a particular status or category.

1. Once you’ve reach the button configuration properties, give the button a descriptive “Label” so that end users know what the button does.

2. Under the Action section, optionally require confirmation. Learn more about configuring button confirmation here. You can also change the “Action” to another available button action type if needed.

3. Under Data, there are two settings to configure:

   1. Templates - Choose a previously configure record template associated with the underlying source table in the base to leverage. If there are no options to choose from, then you will need to follow the steps outlined in this support article first before continuing. Click the cogwheel icon and hover over the name of a template to edit (pencil icon) or show it (eye icon). “Showing” the template connects it to the button you are configuring. Once shown, X out of the record template configuration modal.

   2. After update, move to next record - Toggle this on to move the end user to the next record on their screen after the button has been clicked and the templated record has been created.

4. Next, you can change the Appearance of the button to be another color. By default, Airtable sets this color to be grey.

5. Lastly, configure “Visibility” Rules for the button. Here, you can click the cogwheel icon to set filtering conditions based on your use case’s individual needs. One common use case is to only allow certain users to see this button. Another example would be to only show this button for records associated with a particular status or category.

1. Once you’ve reach the button configuration properties, give the button a descriptive “Label” so that end users know what the button does.

2. Under the Action section, optionally require confirmation. Learn more about configuring button confirmation here. You can also change the “Action” to another available button action type if needed.

3. In the Data section, there are two settings to configure:

   1. Toggle on the “Open in new tab” option to force the interface page to open in a new tab rather than load the page on the current tab. By default, this option is toggled on, but there may be use cases where you want this option off.

   2. Next, choose a “Field” from the underlying table that contains the URL from the record. To modify this, click the dropdown arrow next to this setting.

4. Next, you can change the Appearance of the button to be another color. By default, Airtable sets this color to be grey.

5. Lastly, configure “Visibility” Rules for the button. Here, you can click the cogwheel icon to set filtering conditions based on your use case’s individual needs. One common use case is to only allow certain users to see this button. Another example would be to only show this button for records associated with a particular status or category.

Note

For an automation to be used with the “Run automation” button action, it must include the When a button is clicked automation trigger. Read more about the setup process here.

1. Once you’ve reach the button configuration properties, give the button a descriptive “Label” so that end users know what the button does.

2. Under the Action section, optionally require confirmation. Learn more about configuring button confirmation here. You can also change the “Action” to another available button action type if needed.

3. In the Automation section, click the dropdown menu and choose a compatible automation. Alternatively, click the + Create new automation button and follow the steps outlined here. Name the automation and then click Continue in Automations to start building the automation in a new browser tab.

4. Once a compatible automation has been connected to this button action, you can change the Appearance of the button to be another color. By default, Airtable sets this color to be grey.

5. Lastly, configure “Visibility” Rules for the button. Here, you can click the cogwheel icon to set filtering conditions based on your use case’s individual needs. One common use case is to only allow certain users to see this button. Another example would be to only show this button for records associated with a particular status or category.

1. Toggle on the “Require confirmation” setting in the Action section of a button’s configuration modal.

2. Give the warning box that will appear a “Title” that will help warn end users. By default, this title will appear as “Are you sure?”

3. Next, in the “Message” setting, type out a more descriptive explanation of what the button will do if the user confirms the action by clicking the button. Airtable will auto-generate copy based on the button action type you are configuring, but we recommend double-checking it for accuracy and sophistication.

4. Finally, in the “Button label” setting, choose the text that will appear in the confirmation button. By default, Airtable sets this as “Yes, continue.” Note that a “Cancel” button will always appear for a user to prevent a mistaken button click.

   

1. If this is the first time you've added elements to an interface, please consult this help article first.

2. Find the Button element by clicking + Add element in the lower left portion of the interface editor.

3. You'll then place the element somewhere in the layout of your interface page. Don't worry if it isn't in perfect positioning yet, as you can always move the element later.

4. Next up, you'll need to configure the button's properties so that it performs and looks the way you want it to. This includes properties related to “Button actions" and "Appearance."

You can set a button to perform a maximum of 5 actions at once. The actions performed are all or nothing. There is no "logic" that can be configured for the button

A collaborator can only click on buttons in interfaces that meet their permission levels.

• A read-only or commenter collaborator can only click on buttons with certain action types such as Copy link to record, Go to previous/next record, Go to URL in record, Go to interface page (if they have access to that page), and Go to external URL.

• Read-only and commenter collaborators are not able to click on buttons with the Update record, Delete record, or Run automation actions since they are not allowed to perform those types of actions with their given permission level.