> 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/field-is.md).

# Field is

<figure><img src="https://578966019-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FT2n2w4uDCJvv7CJ5zrdk%2Fuploads%2Fgit-blob-a2adbeed77835a21f19e16a47a4b93e368f4e204%2Fimage.png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

## When to use it

Use this card to check whether a document field is empty or missing, for example when an invoice has no invoice number and needs an additional check. This is a condition; configure the subsequent action separately.

**Where:** Standard workflow → additional conditions (AND) → Document Field.

## Configuration — version 2

| Setting      | Example value                    |
| ------------ | -------------------------------- |
| Field        | `invoice_id` — invoice number    |
| Field status | Empty or missing (`field_empty`) |

Select an actual field configured in your organization. The `field_not_empty` option checks whether the field contains a value.

## Practical example

| Example value                | Expected result for `field_empty`                    |
| ---------------------------- | ---------------------------------------------------- |
| Empty or missing field       | Condition met                                        |
| `DEMO-001`                   | Condition not met                                    |
| Number present but incorrect | Condition not met — the field still contains a value |

These are expected-result examples. Add an appropriate content condition to validate the number itself; this card checks the field state. In version 2, leading and trailing spaces are removed from text before checking whether the field is empty.

## Administrator example video

When I use the card, where to find it and how to detect missing invoice numbers. The administrator, office and voice are synthetic; the demonstration shows the real DocBits interface of a test account. The examples show expected results.

{% embed url="<https://docbits-videos.fra1.cdn.digitaloceanspaces.com/settings-assistant/workflow-card-field-status-admin/v1/en.mp4>" %}

[Open video with English captions](https://docbits-videos.fra1.cdn.digitaloceanspaces.com/settings-assistant/workflow-card-field-status-admin/v1/en.html)

[Read transcript](https://docbits-videos.fra1.cdn.digitaloceanspaces.com/settings-assistant/workflow-card-field-status-admin/v1/en.txt)


---

# 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/field-is.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.
