Skip to main content

​
Overview

Automation Buttons let users start an automation directly from a record details page. Admins place buttons on the record layout and configure which automation runs when the button is pressed. Users see a clear running state, success or failure message, and can provide required inputs via a form when the automation needs them.
An On-Demand trigger must be configured in an app’s automation and the button added to the Record Details Layout for the Automation Button to work. Automations using other trigger types (e.g. scheduled or event-based) cannot be invoked from a button.
Key Capabilities:
  • Buttons on Record Layout - Admins add buttons to the record details layout with a label, button text, and icon
  • Run On-Demand Automations - Each button runs a chosen automation that has an On-Demand trigger; the automation can be from the same aspect or a different one
  • Optional Conditions and Inputs - Configure when the button can be pressed (e.g. based on record data) and which inputs are required; a form is presented to gather inputs before the automation runs
  • Clear Feedback - Success and failure messages when the automation completes; running status is shown while the automation is in progress
  • One Run at a Time - The user cannot trigger the same automation again until the current run finishes

​
Set Up Automation Buttons

​
Prerequisites

Before setting up automation buttons, ensure you have:
  • App Admin access (or equivalent) to edit the app and its record details layout
  • An automation with an On-Demand trigger to run from the button (from this app or another aspect). See Automation System to create automations
  • Familiarity with the Layout Builder for placing the button on the layout

​
Step-by-Step Configuration

To access: Open your app and click Record Details Layout icon Record Details Layout in the left navigation. See Layout Builder for how to work with layouts.
  1. Open the Record Details Layout - Navigate to your app, open Configuration (or App settings), then open Record Details Layout icon Record Details Layout (or the layout where you want the button to appear).
  2. Add an Automation Button to the Layout - In the layout builder, add the Automation button and place it in the section where you want it to appear for users.
  3. Set Button Label, Text, and Icon - Open the button configuration, enter a Label (for your reference in the layout), set the Button Text that users will see (e.g. “Send for approval”, “Generate report”), and optionally select an Icon.
  4. Select the Automation - Choose the automation that runs when the button is pressed. It must use an On-Demand trigger. You can select an automation from the current aspect or from a different aspect (e.g. another app or element).
  5. Configure Availability and Required Inputs - If needed, configure when the button can be pressed (e.g. based on record data such as status). If the automation requires inputs, configure required inputs so a form is shown to the user before the automation runs.
  6. Save the Layout - Save the record details layout so the button appears for users.
Using an automation from a different aspect: You can select an automation that belongs to another app or element. Use this when the same action (e.g. “Notify team”) is reused across multiple record types. The automation still runs in the context of the current record.

​
Button Configuration Options

​
Button Appearance

When adding an automation button to the layout, you can set:
PropertyDescription
LabelAdministrative label for the button (e.g. for layout organization)
Button TextText shown on the button to users
IconOptional icon displayed with the button

​
Choose the Automation

Select the automation that runs when the button is pressed. The automation must use an On-Demand trigger — automations with other trigger types will not appear as options. You can choose an automation associated with the current aspect (app or element) or an automation from a different aspect. The automation runs in the context of the current record when the user clicks the button.

​
When the Button Can Be Pressed

The button can be available at any time, or you can configure visibility or eligibility based on record data (e.g. only when a status field has a certain value). When the automation requires input values, those can be marked as required; the user will see a form to provide them before the automation runs.

​
How Buttons Work for End Users

When a user opens a record that has an automation button:
  1. Click the button - The button appears on the record details page where the admin placed it.
  2. Provide inputs (if required) - If the automation needs inputs, a form is presented. The user fills the required fields and submits.
  3. Running state - While the automation runs, a running status is shown. The user cannot trigger the automation again until the run completes.
  4. Completion - When the automation finishes, a success message is shown on success or a failure message on failure.
Only one run can be in progress at a time for a given button invocation. The button becomes available again after the automation completes (success or failure).

​
Best Practices

  • Use short, clear button text so users understand the action
  • Choose automations that make sense in the context of the record (e.g. “Send for approval”, “Generate report”)
  • Configure required inputs only when the automation needs them; avoid unnecessary form steps
  • Test the button as an end user to confirm the form, running state, and success or failure messages behave as expected

​
Troubleshooting

Possible causes:
  • The layout was not saved after adding the button. Save the record details layout and refresh.
  • Your role may not have access to the layout or the button. Check app and layout permissions.
Check:
  • The automation uses an On-Demand trigger — buttons only work with On-Demand automations
  • The correct automation is selected in the button configuration
  • The automation is published (not in draft)
  • Your user has permission to run the automation
  • If a form was shown, all required inputs were provided and submitted
Check:
  • The button configuration specifies which inputs are required for the automation
  • The automation trigger or steps expect the inputs you configured
  • If you need to change required inputs, edit the button configuration in the layout and update the automation if needed

Layout Builder

Design record page layouts and place automation buttons

Automation System

Learn how automations work and how to build them

Triggers Reference

Trigger types including action-based invocation

Form Builder

Configure forms and fields used for automation inputs