> For the complete documentation index, see [llms.txt](https://docs-embed.anyflow.jp/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-embed.anyflow.jp/solution-editor/triggers/triggers-conditions.md).

# トリガー条件

## **概要**

トリガー条件とは、どのようなトリガーイベントを選択して処理するかを定義する追加のルールです。\
例えば、GoogleDriveの `フォルダにファイル/フォルダが新規作成された際に実行` トリガーで、フォルダが作成された際にはトリガーさせない、といった追加のルールを設定することができます。

<figure><img src="https://files.readme.io/2b951bd-trigger_rule.png" alt="674" width="563"><figcaption><p>is folder が Falseと等しい（ファイルである）場合、トリガーしない設定の例</p></figcaption></figure>

トリガー条件は、トリガーイベントが取得された後にAnyflowによって評価されます。\
トリガー条件に合致する場合のみ、ソリューションが実行されます。トリガー条件に合致しない場合はソリューションは実行されません。

## **トリガー条件の追加**

トリガー条件を追加するには、右ペインのトリガー条件の「+」ボタンを押下し、AND か OR で条件を追加することができます。

<figure><img src="https://files.readme.io/a2b4086-add_trigger_rule.png" alt="" width="563"><figcaption></figcaption></figure>


---

# 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-embed.anyflow.jp/solution-editor/triggers/triggers-conditions.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.
