--- title: "How to: Triggering Operations Using the Button Component" slug: "how-to-triggering-operations-using-the-button-component" updated: 2025-09-25T19:45:22Z published: 2025-09-25T19:45:22Z canonical: "docs.unqork.io/how-to-triggering-operations-using-the-button-component" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.unqork.io/llms.txt > Use this file to discover all available pages before exploring further. # How to: Triggering Operations Using the Button Component ## Overview Using a [Button component](/v1/docs/button-component), you can **trigger any operational component**. This allows your end-user to begin the configured operation with the click of a button on your application. > Discover how to trigger operations in Vega using the Operations Builder tool, view our [Operations Builder](/v1/docs/operations-builder) article. Here are few components a Button can trigger: - [Initializers](/v1/docs/initializer-component) - [Decisions](/v1/docs/decisions-component) - [Data Workflows](/v1/docs/introduction-to-data-workflow) - [Calculators](/v1/docs/calculator-component) - [Plug-Ins](/v1/docs/plug-in-component) ## When to Trigger Operations Using a Button Component There are several use cases where you can use a Button to trigger operations. A few examples include: - Using a Button to trigger a Calculator component after your end-user enters their information. This ensures all the necessary input is there before the Calculator runs. - Using a Button to trigger a Plug-In component's Create Submission or Update Submissions API (application programming interface) call. - Adding custom navigation Buttons to your module. The Buttons can trigger Initializer components that trigger a [Navigation](https://docs.unqork.io/Content/A04-ModEditor-Display_Layout/A04009-Navigation_Component.htm?Highlight=navigation) component. - When you want to improve your application's performance—having many Decisions or other components set to a Watch Trigger Type slows down a page's load time. ## How to Trigger Operations Using a Button Component At the basic level, here's what you'll do to manually trigger a component using a Button component: 1. In the Module Builder, drag and drop a **![Button component Icon](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/button_component_icon(23).png?sv=2026-02-06&spr=https&st=2026-11-08T10%3A18%3A11Z&se=2026-11-08T11%3A18%3A11Z&sr=c&sp=r&sig=HYnSU91%2BtMuoW%2FyAtqGP77VyvvmiiIS3N0e4MsY5mWs%3D) Button** component onto your canvas. 2. Navigate to the **Actions** settings. 3. From the Action Type drop-down, select **Event**. > [!NOTE] > You can use the On Click field with any Action Type selection. Here, we've selected Event, but you could use Save, Save Draft, Validate, or Reset depending on your use case. For more information on these Action Types, you can read the [Button component](/v1/docs/button-component) article in our Documentation Hub. 4. Under Triggers, in the On Click field, enter or select the Property ID of the component you want to trigger. 5. Click **Save Component**. 6. **Save** your module. Let's look at an example. You can see the basic configuration that triggers a **![](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/calculator_teal_component(3).png?sv=2026-02-06&spr=https&st=2026-11-08T10%3A18%3A11Z&se=2026-11-08T11%3A18%3A11Z&sr=c&sp=r&sig=HYnSU91%2BtMuoW%2FyAtqGP77VyvvmiiIS3N0e4MsY5mWs%3D) Calculator** component called **calcAge**. The Action Type is set to `Event` and, in the **On Click** field, the Calculator's Property ID, **calcAge**, is entered. [![A static image displaying the Button component's Action Type and Triggers setting.](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/example_btn_1_thumb_0_0.jpg?sv=2026-02-06&spr=https&st=2026-11-08T10%3A18%3A11Z&se=2026-11-08T11%3A18%3A11Z&sr=c&sp=r&sig=HYnSU91%2BtMuoW%2FyAtqGP77VyvvmiiIS3N0e4MsY5mWs%3D)](https://cdn.us.document360.io/15548f06-2fba-434c-b0c1-5df88317dbd7/Images/Documentation/example%20btn%201.jpg?sv=2026-02-06&spr=https&st=2026-11-08T10%3A18%3A11Z&se=2026-11-08T11%3A18%3A11Z&sr=c&sp=r&sig=HYnSU91%2BtMuoW%2FyAtqGP77VyvvmiiIS3N0e4MsY5mWs%3D) After saving both components, your Calculator will only run after the end-user clicks the Button. ## Resources - [Additional Secondary Field Components](/v1/docs/introduction-to-secondary-fields). - [Triggering Decisions with Buttons](/v1/docs/how-to-trigger-decisions-with-buttons). - [Creating Custom Navigation Buttons](/v1/docs/use-case-custom-navigation-buttons). - [Triggering Initializers with Buttons](/v1/docs/use-case-triggering-initializers-with-buttons). - [Triggering Multiple Components Using a Single Button](https://community.unqork.com/platform-q-a-10/multiple-component-triggering-through-button-post-trigger-9359). End-users, also known as Express Users, are the individuals accessing an application through Express View. In most cases, end-users are the customers using the product. The Vega (v 2.0.0) runtime is the next-generation engine of the UDesigner platform. Vega uses cutting-edge technologies to improve the Creator and end-user experience. The action performed by the button when selected. Enter the Property ID of the component that you want to trigger on each button-click. A Property ID is the unique field ID used by Unqork to track and link components in your module.