> For the complete documentation index, see [llms.txt](https://docs.helmut.de/helmut4-releases/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.helmut.de/helmut4-releases/v4.8.0/helmut4-components/streamdesigner/nodes/conditions/misc-5/wildcard-condition.md).

# Wildcard Condition

With the help of the Wildcard Condition it is possible to replace any other condition, respectively to match any source against any value. This value can be fixed or defined via a wildcard.

For example, it would be conceivable to use this to replace the user condition by simply entering the user name and matching it with {user.name}. Since this node exists, this is of course pointless. A more sensible use case would be to match the {job.source} in a stream against a predefined extension, for example .MXF.

Be creative.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.helmut.de/helmut4-releases/v4.8.0/helmut4-components/streamdesigner/nodes/conditions/misc-5/wildcard-condition.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.