> For the complete documentation index, see [llms.txt](https://docs.adapptio.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.adapptio.com/getting-started/architecture-overview/actions.md).

# Actions

*Actions* represent a business logic of a broad spectrum of functions wired together in the *Flow Canvas*. They are commonly used to connect integrations, execute javascript code, and pass data to *Views* and vice versa.

*There exist three ways how to work with Actions in Adapptio.*

### 1. Binding a Data Source

*Adding Data from Action* provides a connection between *Views* and *Actions*, which can be referenced as a data source for any required component. *Action* must have `LOADED` status or be reloaded by the **Update State** *Method* from Events.

{% tabs %}
{% tab title="Outline Panel" %}
![](/files/m7mSIjP5XwFCZZnABBa3)
{% endtab %}

{% tab title="Inspector" %}
![](/files/xxgPZG5S71Lgg6kGfFE4)
{% endtab %}

{% tab title="Data Explorer" %}
![](/files/LX4Wt6FHoSfQS4nGKoLe)
{% endtab %}

{% tab title="Event\[Update State]" %}
![](/files/FiWSS4ysPDH0xBQY01x1)
{% endtab %}
{% endtabs %}

### 2. Calling an Action from an Event

The following way to call *Actions* is by the **Call Action** *Method* from *Events*. Any existing components can trigger it depending on the required *Event Logic*.

{% tabs %}
{% tab title="Event\[Call Action]" %}
![](/files/PP5EI4Bs6buYrv8cl91z)
{% endtab %}

{% tab title="Call Action\[Settings]" %}
![](/files/FlarRtcZx4Fe0ZZKbWKU)
{% endtab %}
{% endtabs %}

### 3. Scheduling an Action

Scheduling *Actions* are independent of any superior Views and are executed once or in specific intervals at the backend.

{% tabs %}
{% tab title="Action Settings" %}
![](/files/kS1z3S9fFW9oLyUGUGAH)
{% endtab %}
{% endtabs %}