> For the complete documentation index, see [llms.txt](https://docs.docbits.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docbits.com/administration-and-setup/workflow/cards-overview/and/document-field/if-country-in-field-is-one-of.md).
# If Country in Field is One of
Use this condition when an additional processing step should apply to documents from selected countries, for example Germany and France. The card compares the country read from a document field with a configured country list.
**Where:** Standard workflow → additional conditions (AND) → Document Field. Configure the subsequent action separately under THEN.
## Configuration — version 2
| Setting | Value |
| -------------- | -------------------------------------------------- |
| Field | An existing text field containing the country name |
| Operator | `is` |
| Countries | `Germany, France` |
| Continue value | `true` |
## Practical example
| Country field value | Expected condition |
| ------------------- | ------------------ |
| `Germany` | Met |
| `France` | Met |
| `United States` | Not met |
The country names shown as code are fixed input values for this example.
## Limits and checks
`false` does not invert the comparison. Even a matching country does not produce a positive condition with that setting. To check the opposite condition, select `isnot` with `true`.
Handle missing fields and empty country values separately; they can return a missing-data result rather than an ordinary non-match.
Source inspection of the development version dated 22 October 2026 shows a conversion error for ISO inputs such as `DE` and `DEU`. These examples therefore use full country names. Check ISO-code handling separately in your installed version.
---
# 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.docbits.com/administration-and-setup/workflow/cards-overview/and/document-field/if-country-in-field-is-one-of.md?ask=&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.
