> For the complete documentation index, see [llms.txt](https://readme.directual.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://readme.directual.com/scenarios/principles-of-scenarios.md).

# Understanding Directual Scenarios

{% hint style="info" %}
101-course: [The basics of Directual scenarios](https://www.directual.com/101-crash-course/scenarios-the-basics)
{% endhint %}

Directual scenarios are a crucial component of your application's back-end logic. Scenarios manage and process data based on specified criteria.

{% embed url="<https://youtu.be/MdfWP8NhMpQ>" %}

Directual scenarios process objects in a **target data structure**. You can select the **target data structure** when configuring the **START step:**

![Choosing target structure for scenario](/files/-M6iF-WWjFIOGbrtioct)

## Types of triggers

Directual scenarios offer two primary types of triggers:

* [Real-time, event-](/scenarios/event-driven-triggers.md)[based](/scenarios/event-driven-triggers.md) (as a reaction to an [event](/scenarios/principles-of-scenarios/directual-event-model.md)): These scenarios respond to specific events, such as user actions or changes in the application's data. For instance, a scenario can be triggered when a user submits a form.
* [Schedule](/scenarios/schedule-triggers.md)[d](/scenarios/schedule-triggers.md): Scheduled scenarios run at predefined times or intervals, providing you with the ability to automate tasks. For example, you can schedule a scenario to execute every Monday at 4:40 p.m. GMT.

Additional trigger options:

* [Calling scenarios from within scenarios](/scenarios/editing-scenarios/system-steps/link-scenario-step.md): You can execute one scenario from another using the Link scenario step, creating complex workflows by chaining scenarios together
* [Synchronous scenarios](/scenarios/synchronic-scenarios-1.md): These scenarios respond to synchronous POST requests and process incoming data, returning it as an API response

{% hint style="info" %}
Note that a single scenario has the capability to incorporate all available trigger types!
{% endhint %}

![An example of a scenario which combines different trigger types](/files/-MBcj43lX0YFMwPiehBr)