> For the complete documentation index, see [llms.txt](https://docs.notionapps.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.notionapps.com/customize-app/type-of-components/button-component.md).

# Button Component

{% hint style="warning" %}
As a third-party provider, NotionApps does not have access to the Notion "Button" database property. There are workarounds possible to trigger your Notion automation directly from NotionApps. Those workarounds involve creating a new property and changing that property from inside NotionApps. On Notion, the property change can trigger the relevant automation.
{% endhint %}

This component triggers certain actions from within your app. The current set of actions include:

1. Dial phone
2. Send email
3. Send SMS
4. Open Link
5. Go To Screen

We will support the following actions in the future:

* "Open Edit Screen" → opens an edit item screen
* "Change Data" → changes data in the current item and saves the item 


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.notionapps.com/customize-app/type-of-components/button-component.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.