Button fields let you add actions to SmartSuite views and records, giving users control over when those actions are triggered. Buttons can be used to open links, navigate to related resources, trigger automations, create new records, or open a form — directly from a record.
The Open URL action allows you to configure a destination that opens when clicked. URLs can be static or dynamically generated based on field values in the record. This makes it easy to link to external systems, perform searches, or open context-specific resources.
Button fields can also be configured to execute automations, enabling workflows that act on record data with a single click. SmartSuite ensures these actions always use the most up-to-date record information.
Additional action types, such as sending emails or performing record-level operations, will be added over time.
Plan Availability | All plan types |
Permissions | Solution Creators - Can create, modify, delete, and manage buttons. |
Related Reading |
Adding a Button Field
From Grid View
Navigate to your Grid View.
Click the + Add Field button.
Select Button from the field options.
Configure the field properties as needed.
From Record View
Open a record.
Click the + Add Field option within the record.
Select Button from the available field types.
Set up the field properties as required.
Field Properties
The button field’s properties allow you to configure:
Display Format: Customize how the button looks.
Button Label: Define the text displayed on the button.
Button Color: Choose the button’s color.
Action Type: Select the action triggered when the button is clicked.
Open URL: Can be clicked by any user with viewer access.
Execute Automation: Can only be clicked by users with edit rights.
Create a Record: Opens a new record — optionally pre-filled — in any table. Can only be used by users with create rights.
Open a Form: Opens a SmartSuite form from the record. Can be used by any user with access to the form.
Button Behavior on Record Pages
When a button is clicked from a Record Page, SmartSuite ensures the action runs against the most current version of the record.
Automatic Save Before Execution
When triggering an automation from a button, SmartSuite automatically attempts to save the record in the background.
This prevents automations from running with outdated or incomplete data.
Handling Unsaved Changes
If the record has unsaved changes:
A confirmation modal appears with options to:
Save and run the automation
Run without saving
Cancel the action
Required Field Validation
If required fields are missing, you’ll see the standard validation messages.
The automation can only run after required data is completed and saved.
Activity Tracking
When an automation runs after a successful save, the action is recorded in the record’s activity history for auditing and traceability.
This behavior applies automatically and requires no additional configuration.
Open URL Action
The Open URL action opens a web page in a new tab when clicked. URLs can be static or dynamically generated with a formula. Choose the type by clicking on the Static URL or URL Formula option.
Static URL
Use this option for URLs that don’t change.
Clicking the button will open the specified URL in a new browser tab.
URL Formula
Customize URLs dynamically using the SmartSuite Formula Builder.
Combine field values, operators, functions, and text to generate the URL.
If the formula is invalid, an “Invalid Syntax” message will appear.
Learn more about formulas in the Formula Field Article.
Examples
Simple Dynamic Links
Use the URL stored in another field or create a custom link based on record data.
Conditional Logic for URLs
Create logic to generate URLs based on record type or status. For example:
If the task type is "Branding," the button links to the Branding Guidelines view.
If the task type is "Content," it links to the Content Guidelines view.
Buttons without a defined link remain unclickable.
Create a Record Action
The Create a Record action lets a button open a new, optionally pre-filled record without leaving the current record. This turns a record into a guided entry point for related workflows — launching a follow-up task, logging an incident, or starting a request.
The record is only created after the user clicks Save.
How to set it up
In the Button field's properties, set Action Type to Create a Record.
Choose where the record goes: select the Solution and Table. By default, it uses the current table.
Set default field values (optional): add fields and choose the values to pre-fill so users don't have to. For example, set Status = New, or assign to a specific team. These values appear automatically when the record opens.
What you can pre-fill
You can set static defaults for most field types, including text and numbers, dates and times, status and dropdowns, checkboxes (Yes/No), assigned users, tags and colors, and addresses.
Not supported: linked records, file uploads, signatures, and time tracking. Dynamic values (such as current user or current date) are not available — defaults are static values only.
Which values take priority?
If a field has defaults set in more than one place, button values win, then template defaults, then field-level defaults.
Permissions
The action follows existing permissions. If a user can create records they can use the button; if not, the button is hidden or disabled.
Open a Form Action
The Open a Form action opens a SmartSuite form directly from a record — useful for self-service entry points like service requests, escalations, or change requests, where you want users to submit through a controlled form layout.
How to set it up
In the Button field's properties, set Action Type to Open a Form.
Choose the source: select the Solution and Table.
Select the form: choose from the available forms (listed A–Z). A form selection is required.
Choose where it opens using the Open In option:
Popup (default)
Slider
Fullscreen
New Tab
Practical Scenarios and Use Cases
Departmental Collaboration
Scenario: The Marketing team needs quick access to campaign guidelines.
Solution: Add a button field to link directly to the relevant guidelines based on task type.
Workflow Efficiency
Scenario: A team frequently accesses third-party tools related to tasks.
Solution: Use URL Formulas to create dynamic links to those tools based on task information.
Data Integration
Scenario: A support team needs to view customer details stored in another system.
Solution: Add buttons that generate links to customer profiles using stored IDs.