> For the complete documentation index, see [llms.txt](https://docs.novacura.com/flow-ifs-cloud-development-guidelines/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.novacura.com/flow-ifs-cloud-development-guidelines/flow-development-with-odata/trigger-flows-from-ifs-cloud.md).

# Trigger Flows from IFS Cloud

There are different options and scenarios for triggering a Flow from IFS. It could be triggered via **Event Actions**, via **projection execution's** or **Commands.** The different scenarios are covered to the following sub sections. 

### Button commands in IFS Cloud

In IFS cloud there’s no RMB option. Instead, you must use custom buttons, called “commands”, to achieve the same functionality. Button commands can be of different types: 

* **Execute Action** - Call an existing Method in IFS Cloud.
* **Navigation Link** - Provides the functionality to navigate between pages with or without parameters.
* **External Navigation Links** - Provides the functionality to navigate to an external URL, with or without parameters.
* **Execute Quick Report** - Provides the capability to execute a quick report.
* **Execute Operational Report** - Provides the capability to execute an operational report.
* **Execute Workflows** - Provides the capability to execute workflows with parameters.


---

# 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.novacura.com/flow-ifs-cloud-development-guidelines/flow-development-with-odata/trigger-flows-from-ifs-cloud.md?ask=<question>&goal=<user_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.