> 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/date-and-time/today.md).
# Today
Version 2 example: Greater or Equals, 2026-11-01. The comparison uses today's UTC date.
## What this card checks
This condition compares **today's UTC date at workflow execution** with a configured date. The time of day is ignored. Use it under **And → Date & Time** for a date cutoff or rollout rule.
## Configuration
Select the required comparison: equals (`eq`), not equals (`neq`), after (`gt`), on or after (`ge`), before (`lt`), or on or before (`le`). Enter an explicit date such as `2026-11-01`.
## Practical example
**When to use:** Allow a following action only from a planned rollout date onward.
**Configuration:** Choose **Greater or Equals** (`ge`) and `2026-11-01`.
**Expected result:** On `2026-11-01` UTC the condition is met, and it remains met on `2026-11-02` UTC. On `2026-10-31` UTC it is not met. The document's own dates do not determine this comparison.
Configure the workflow trigger and the following action separately. To evaluate a time window, use the separate Date or Time card.
---
# 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/date-and-time/today.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.
