> For the complete documentation index, see [llms.txt](https://docs.diaflow.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.diaflow.io/workflow-builder/nodes/trigger/automatic-trigger/on-app-event.md).

# On app event

**On app event** is an **Automatic trigger**.

It starts your workflow when something happens in another app.

For example, a workflow can start when a new row is added, a file is uploaded, or a calendar event is created.

<figure><img src="/files/QfH5aaqquPwLNauxZVMl" alt=""><figcaption></figcaption></figure>

## When to use it

Use **On app event** when you want your workflow to run automatically from business activity.

This is useful when your team works in tools like tables, email, storage, calendars, or other connected apps.

## How it works

1. Add a **Trigger** node.
2. Choose **On app event** as the type.
3. Select the app you want to monitor.
4. Choose the event that should start the workflow.
5. Complete the fields shown for that app.

Once the event happens, Diaflow starts the workflow automatically.

## Choose an app

After you select **On app event**, you can choose the app you want to receive the trigger from.

There are multiple apps available to choose from.

You can search for an app, browse built-in apps, or pick from the available trigger apps list.

The selected app becomes the source that tells Diaflow when to start the workflow.

## Choose the trigger event

After you choose an app, you select the event that should trigger the workflow.

This is the action you want Diaflow to watch for.

Common examples include:

* A new record is created.
* An existing record is updated.
* A file is added.

The available events depend on the app you selected.

## Fill in the fields below

After you choose the app, more fields appear below.

These fields help Diaflow understand exactly what to watch.

For example, you may need to choose:

* A table
* A sheet
* A folder
* A calendar
* A specific trigger event

The field names change based on the selected app.

You only need to choose the options that match your use case.

## Example

If you choose **Diaflow Tables**, you can decide:

* which table to use
* which sheet to use
* which event should trigger the workflow

For example, you can start a workflow every time a **New Row** is created.

## Why teams use it

* It removes manual work.
* It helps teams react faster.
* It keeps processes consistent across apps.

## Good to know

* **On app event** belongs to **Automatic trigger**.
* The available fields depend on the selected app.
* The available events also depend on the selected app.
* You can change the app later if needed.

### Next steps

* Learn how **Trigger** works in [Trigger](/workflow-builder/nodes/trigger.md).
* Compare it with [Schedule](/workflow-builder/nodes/trigger/automatic-trigger/schedule.md).
* Compare it with [Webhook](/workflow-builder/nodes/trigger/automatic-trigger/webhook.md).