> ## Documentation Index
> Fetch the complete documentation index at: https://docs.b3os.org/llms.txt
> Use this file to discover all available pages before exploring further.

# One-Time Schedule

Run your workflow once at a specific date and time.

Trigger Schedules

Run your workflow once at a specific date and time.

## At a Glance

| Field | Value |
| --- | --- |
| Trigger ID | `schedule` |
| Category | Schedules |
| Tags | `schedule`, `time-based`, `one-time`, `scheduled` |

## Trigger Configuration

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `nextRunAt` | `string` | Yes | UTC timestamp in RFC3339 format \(e.g., 2025-10-28T22:00:00.000000Z\) |

## Trigger Result

| Field | Type | Required | Description |
| --- | --- | --- | --- |
| `triggeredAt` | `string` | Yes | Actual timestamp when the schedule was triggered \(UTC, RFC3339 format\) |

## Workflow Root Example

```json
{
  "nodes": {
    "root": {
      "type": "schedule",
      "payload": {
        "nextRunAt": "2026-04-25T12:00:00.000000Z"
      },
      "children": [
        "log_event"
      ]
    },
    "log_event": {
      "type": "log",
      "payload": {
        "message": "Triggered at {{$trigger.triggeredAt}}"
      },
      "children": []
    }
  }
}
```

**Reference trigger output**

Downstream nodes can use `{{$trigger.triggeredAt}}` and any result fields listed above. Event triggers usually expose the raw source payload under a field such as `event`, `body`, `trade`, or `raw`.