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

# Feed

> Review automated Clara prompt results, manage schedules, and optionally email outputs to your team.

**Feed** is where Clara delivers scheduled prompt results on a timeline. Use the **Schedules** tab to create recurring or one-time prompts, control who can see them, and optionally email results to teammates.

<Note>
  Feed and Schedules require the **Inform** plan (or an active Inform trial). Without that entitlement, the page shows an upgrade prompt instead of your feed.
</Note>

## Get started

1. Sign in to [nOps](https://clara.nops.io/dashboard).
2. In the sidebar, open **Feed**, or go to [clara.nops.io/feed](https://clara.nops.io/feed).
3. On the **Schedules** tab, click **New schedule** to create your first automated prompt.
4. When Clara runs the prompt, the result appears on the **Feed** tab.

## Key features

### Feed tab

The default view lists scheduled prompt runs for your organization, newest first.

* **Category chips** narrow the list: All, FinOps Analyst, Anomaly Detection, Waste, Recommendations, or Budgeting.
* Each **result card** shows the schedule name, category badge, and relative time. A status badge (Queued, Running, Failed, or Skipped) appears while a run is in progress or didn't succeed; completed runs show no status badge at all.
* **Collapsed preview** — summary text, an error message, or a chart/table preview when Clara returned structured output.
* **Expand a card** (completed or failed runs) to read the full response, including multi-turn follow-ups when the run produced a thread.
* **Open in Clara** — on completed chat runs, resume the conversation in the Clara side panel.
* **More actions** — edit the parent schedule or delete the result (delete requires the appropriate permission).
* **Empty state** — if you have no runs yet, use **Create a schedule** to set up your first automation.

The feed refreshes automatically while you stay on the page.

### Schedules tab

Switch with the **Schedules** tab (or open `/feed?tab=schedules`).

* **New schedule** opens the schedule dialog.
* **Category** and **scope** filters narrow the list (the **Global** scope filter appears only for super-admins).
* Each **schedule row** shows the name, prompt text, scope and category badges, paused state, and an **Email** badge when email delivery is on.
* **Metadata** includes cadence, linked canvas name (or standalone chat), and next run time when applicable.
* **Actions** (based on your permissions):
  * **Enable/disable** toggle — pause or resume automation.
  * **Run now** — queue an immediate run; check Feed for the output.
  * **Edit** — open the schedule dialog.
  * **Delete** — remove the schedule and its run history.

### New or edit schedule dialog

Use **New schedule** or **Edit** on an existing row.

| Field                     | What it does                                                                                                                  |
| ------------------------- | ----------------------------------------------------------------------------------------------------------------------------- |
| **Name**                  | Display name for the schedule and feed cards.                                                                                 |
| **Prompt**                | The instruction Clara runs on each execution.                                                                                 |
| **Scope**                 | **Private** (you), **Shared** (organization — admin), or **Global** (super-admin).                                            |
| **Canvas**                | Optional link to a canvas for data context; omit for standalone chat.                                                         |
| **Category**              | FinOps Analyst, Anomaly Detection, Waste, Recommendations, or Budgeting.                                                      |
| **Schedule**              | One-time (specific date and time) or recurring (daily, weekly, or monthly with time and timezone).                            |
| **Enabled**               | When off, the schedule does not run until re-enabled.                                                                         |
| **Email results**         | Optional delivery to selected org recipients with an optional custom subject.                                                 |
| **Send to Slack / Teams** | Optional delivery of the run result to connected [Slack or Teams](/platform/slack-and-teams) channels on each successful run. |

## Filters and controls

### Feed tab

* **Category** — chip filter across all five FinOps categories plus All.

### Schedules tab

* **Category** — same category chips as Feed.
* **Scope** — All, Shared, Private; Global (super-admins only).

## Automation lifecycle

1. **Create a schedule** on the Schedules tab — name, prompt, cadence, and optional canvas or email settings.
2. **Wait for the run** — Clara queues and executes the prompt; status moves from Queued → Running → Completed (or Failed).
3. **Review in Feed** — expand the card for the full response; use previews for a quick scan.
4. **Iterate** — edit the schedule, run now, pause with the toggle, or delete when no longer needed.
5. **Follow up** — use **Open in Clara** on chat results to continue the thread in the side panel.

## What you can automate

Feed and Schedules support recurring FinOps workflows powered by Clara:

* **Scheduled cost and usage analysis** — run the same prompt on a daily, weekly, or monthly cadence and review outputs in one place.
* **Anomaly and waste monitoring** — use category-tagged prompts (for example, Anomaly Detection or Waste) to keep watch on spend patterns.
* **Canvas-linked context** — attach a schedule to a canvas so Clara runs with that canvas's data context, or leave it unlinked for standalone chat.
* **Email delivery** — send completed results to teammates without asking them to open the app.
* **Slack / Teams delivery** — post completed results to connected [Slack or Teams](/platform/slack-and-teams) channels on each run.
* **Continue conversations** — open completed chat runs in the Clara panel to dig deeper without re-running the schedule.

## FAQs

<AccordionGroup>
  <Accordion title="What is the difference between Feed and Schedules?">
    **Feed** shows the latest results from scheduled Clara prompts — completed, running, failed, or queued runs in chronological order. **Schedules** is where you create, edit, enable, pause, or delete the prompts that produce those results.
  </Accordion>

  <Accordion title="How do I follow up on a feed result with Clara?">
    For completed chat-type runs, use **Open in Clara** on the result card. That opens the Clara side panel with the same conversation so you can ask follow-up questions. There is no inline chat input on the Feed page itself.
  </Accordion>

  <Accordion title="Can I automate prompts to run on a schedule?">
    Yes. On the **Schedules** tab, click **New schedule**, write your prompt, and choose a cadence (daily, weekly, monthly, or one-time). Results land in **Feed** automatically. You can also **Run now** from the schedule list or pause a schedule with the enable/disable switch.
  </Accordion>

  <Accordion title="What filters are available?">
    On **Feed**, filter by **category** (FinOps Analyst, Anomaly Detection, Waste, Recommendations, Budgeting). On **Schedules**, filter by **category** and by **scope** (All, Shared, Private; **Global** appears only for super-admins).
  </Accordion>

  <Accordion title="Who can see and manage schedules?">
    Schedules have a **scope**. **Private** schedules are visible to you (org admins can also manage). **Shared** schedules are visible to everyone in your organization (admins create these). **Global** schedules are nOps-provided prompts visible across clients (super-admins only). Run results in Feed respect the same visibility rules as their parent schedule.
  </Accordion>

  <Accordion title="Can results be emailed?">
    Yes. When creating or editing a schedule, turn on **Email results**, pick recipients from your organization, and optionally set a custom subject. An **Email** badge on the schedule row indicates when delivery is enabled.
  </Accordion>

  <Accordion title="Can results go to Slack or Teams?">
    Yes. If your organization has connected Slack or Microsoft Teams in **Settings → Notifications**, turn on **Send to Slack / Teams** in the schedule dialog and pick channels. Completed results post to those channels on each successful run. See [Slack & Teams delivery](/platform/slack-and-teams) for setup.
  </Accordion>
</AccordionGroup>

## Related

* [Budgets](/operate/budgets) — set spend targets and alerts (requires the Operate plan)
* [Explorer](/inform/explorer) — dynamic cost analysis that complements Clara workflows
* [Insights](/inform/insights) — cost savings opportunities and cost anomalies Clara can reference in prompts
* [Canvas](/clara/canvas) — link a schedule to a canvas for data context