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

# Scheduler Node

> Trigger workflows on a schedule—always outputs current UTC time for logging, reporting, and automation.

## What It Does

* **Triggers workflows at set times** — hourly, daily, or custom intervals.
* Adds a **UTC timestamp** to every workflow run for logging and audit trails.
* Provides a structured JSON of **UTC-based time details** (year, month, day, hour, minute, second, timezone).
* Powers **time-based automations** like daily reports, SLA checks, and pipeline snapshots.

***

## Output

The Scheduler Node outputs a dataset with one column:

| Column | Description                                     |
| ------ | ----------------------------------------------- |
| `data` | JSON string containing current UTC time details |

### Example JSON:

```json theme={null}
{
  "timestamp": "2025-07-25T14:07:00.087Z",
  "Day of week": "Friday",
  "Year": "2025",
  "Month": "July",
  "Day of month": "25",
  "Hour": "14",
  "Minute": "07",
  "Second": "00",
  "Timezone": "UTC"
}

```

<Note>
  If your table already has a `data` column, the system auto-renames it (e.g., `data_1`).
</Note>

***

## How It Works

1. Reads your schedule configuration.
2. At the scheduled time, triggers the workflow.
3. Captures the **current UTC time** at that exact moment.
4. Formats time details into JSON (timestamp, date, time, timezone).
5. Outputs the dataset with the `data` column for downstream use.

***

## 🚀 Example Use Cases & Prompts

| Use Case              | Setup Example                                    |
| --------------------- | ------------------------------------------------ |
| Daily Pipeline Report | Trigger every morning at 8am; timestamp report   |
| SLA Monitoring        | Run every hour; log cases missing SLA deadlines  |
| Weekly Snapshots      | Trigger Fridays at 5pm; export pipeline snapshot |
| Activity Logging      | Add timestamps to audit trails automatically     |

***

## ✨ Pro Tips

<Tip>
  **Use clear column names.** Rename `data` → `execution_time` downstream to make logs and reports easier to read.
</Tip>

<Tip>
  **Adjust for your local timezone.** Since output is always in UTC, apply conversion downstream if your team works in a different timezone.
</Tip>

***

## ⚠️ Important Considerations

<Warning>
  The Scheduler always captures the **execution time in UTC**. It does not generate “future” times.
</Warning>

<Warning>
  If your reporting or SLAs are based on local business hours, you’ll need to convert from UTC downstream.
</Warning>

***

## 🛠 Troubleshooting & Gotchas

| Symptom                     | Likely Cause               | Quick Fix                         |
| --------------------------- | -------------------------- | --------------------------------- |
| Workflow doesn’t trigger    | Schedule misconfigured     | Double-check your schedule format |
| Time doesn’t match local TZ | Scheduler outputs UTC      | Add conversion logic downstream   |
| Column renamed to `data_1`  | Naming conflict in dataset | Rename output column for clarity  |

***

## 📝 FAQ

<AccordionGroup>
  <Accordion title="Can I trigger at specific times of day?">
    ✅ Yes — set daily or hourly schedules, or use cron expressions for precision.
  </Accordion>

  <Accordion title="Can I change the timezone?">
    No — output is always UTC. Convert downstream if you need local time.
  </Accordion>

  <Accordion title="Does this node consume credits?">
    Yes, this is a listening node and all listening nodes take 1 Credit.
  </Accordion>
</AccordionGroup>

***

## 💰 Pricing

| Action                 | Credit Cost   |
| ---------------------- | ------------- |
| Workflow trigger event | 1 credit each |

<Note>
  The Scheduler Node consumes **1 credit per scheduled trigger** (e.g., hourly, daily).\
  Any downstream processing may add additional credits depending on nodes used.
</Note>

***

<p style={{ fontSize: '1rem', fontWeight: 'bold', marginTop: '1.5rem' }}>
  ⏰ Put the Scheduler Node at the top of your workflow to run tasks automatically—hourly, daily, or on any schedule you set. 🚀
</p>