> 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/when/page.md).

# Document Type Operation

<figure><img src="/files/2F1C7gy1Q3L9gLmDMS6l" alt=""><figcaption></figcaption></figure>

## **Purpose:**

This workflow card is specifically designed to perform predefined operations on documents categorized by type. It streamlines the handling of various document forms within an ERP system, ensuring that each type is processed according to its unique requirements and organizational policies.

## **Functionality:**

* **Document Type Validation**: This card verifies if a document matches a particular type, enabling users to confirm its categorization.
* **Operator**: Users can set conditions to determine the document's type. Available operators include:
  * **Is**: Confirms that the document matches the specified document type.
  * **Is Not**: Ensures that the document does not match the specified document type.
* **Document Types**: Supported document types include:
  * **Invoice**
  * **Debit Note**
  * **Credit Note**
  * **Purchase Order**
  * **Order Confirmation**
  * **Advance Shipment Notice**

## **Usage**:

This card is useful for document managers and administrators who need to ensure that documents are correctly classified for streamlined processing. Validating document types enhances workflow automation, enables document-specific actions, and keeps records organized.

## **Example Scenario**:

* A user uploads a document labeled as a "Debit Note." Using the "Is" operator, the card confirms that the document type is indeed "Debit Note," allowing the system to apply relevant processing rules and categorize it appropriately.

By deploying the "Document Type" card, organizations can automate document classification, ensure consistency in document handling, and improve the efficiency of document management workflows.


---

# 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.docbits.com/administration-and-setup/workflow/cards-overview/when/page.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.