> For the complete documentation index, see [llms.txt](https://docs.powertable.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.powertable.com/explore-powertable/working-with-powertable/column-setup/add-visual-column/button-column.md). # Button Column A button column is an interactive column that can be added to your table and configured to open a URL or execute an [automation](/explore-powertable/automation.md). 1. To add a new column, go to **Setup > Columns.**

Set up column

2. Click **Add Visual Column > Add Button Column.**

Add button column

Alternatively, you can insert a new column from the 'Home' tab, as shown below:
3. Enter the details about the column: * **Column Name:** Enter a name for the column. * **Label:** The default label is 'Click Here'. If necessary, you can edit the label for the displayed link. * **Action:** Choose the action you want PowerTable to perform when you click the link. You can choose to open a URL or execute an automation, as required.

Column Details

4. **URL:** If you choose to open a URL, enter the URL details in the section below. Choose **Static** to enter a static URL, or **Formula** to enter a formula to generate a dynamic URL based on data. #### Static URL - example
#### Formula - example
5. Click **Save.** The button column is added as shown below:
--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.powertable.com/explore-powertable/working-with-powertable/column-setup/add-visual-column/button-column.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.