# Project Extension Condition With the help of the Project Extension Condition it is possible to use the project extension of the project for which the stream was triggered as a condition for further actions. For example, if you want to make the behaviour of the stream triggered by the “duplicate project” trigger dependent on whether it is a specific project type, you would enter the name of the extension for which the behaviour should change in this node. Here the way can be defined. For example, if the node is to be successful if it is a certain project type, one would use "is" as a condition. If the node is to fail if it is a certain project type, it would be you can use "is\_not". This makes it possible to decide precisely whether the behaviour should apply to a project type or not. The project extension condition can always be queried if the object for which the stream in which this node is used was triggered is a project. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.helmut.de/helmut4-releases/v4.6.0/helmut4-components/streamdesigner/nodes/conditions/project/project-extension-condition.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.