> 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/date-or-time.md).
# Date or Time
Version 2 example: Is, 2026-11-01 09:00:00 to 2026-11-01 17:00:00 (UTC).
## What this card checks
This condition compares the **current UTC date and time when the workflow reaches the card** with two configured bounds. Use it under **And → Date & Time** to restrict a following action to a planned time window.
## Configuration
Choose `is` for a time inside the window or `isnot` for a time outside it. Enter the start and end as explicit UTC date/time values. For a same-day window with the start before the end, both bounds are included.
## Practical example
**When to use:** Allow a maintenance follow-up only during a planned window.
**Configuration:** Select `is`, start `2026-11-01 09:00:00` and end `2026-11-01 17:00:00`, all in UTC.
**Expected result:** A workflow reaching this card at `2026-11-01 10:00:00` UTC meets the condition. At `2026-11-01 18:00:00` UTC it does not. Configure the workflow trigger and the following action separately.
## Timezone and overnight limits
Use UTC values throughout. Adding a timezone suffix does not convert a local time to UTC in the reviewed version 2 parser.
For an overnight window such as `22:00:00` to `04:00:00`, the reviewed version 2 implementation excludes the exact start and end instants from `is`. Check both boundaries before using an overnight rule. The example above uses a same-day window.
---
# 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/date-or-time.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.
