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

# Automation

> New automation lets you configure the workflows your Starter Agent should run — on a schedule or on demand. Platform sample templates help you learn; then adapt or build your own.

**New automation** is the power move: you decide what the agent should do, on what schedule (or on demand), with which sources, model, and notify options — then save that as a **definition** (one saved automation) your **HeroBoost Starter Agent** can run without you staying in chat.

The platform ships a few **sample templates** (ready-made prefills) so you can learn the panel quickly — for example **Channel pulse**, **Scheduled publish**, and **Research digest**. Those samples are onboarding shortcuts, not the limit of the feature. After you pick a template — or start blank — you can edit every field; a template only fills the form once.

Open chat → switch the side panel to **Automation**.

> [!NOTE]
>
> Automation is **hero-owner only** (hidden in subscriber chat). Some templates and outbound publishing may be limited by product access / whitelist while the track finishes smoke testing — if a control is missing, it is not available on your account yet.

## What Automation is for

| You want… | Automation helps by… |
| - | - |
| Recurring work without babysitting chat | Running definitions on a schedule or when you trigger a run |
| A starting point that matches a common job | Prefilling from a **built-in** or **My templates** sample |
| Full control | Editing the definition after save — schedule, sources, model, capabilities, notify options |

**Templates** vs **definitions:** a template is prefill only. After save, the product may remember which sample you started from; it does not lock you into that workflow type forever.

## Words on the panel

| Label | Meaning |
| - | - |
| **Enable automation** | Master switch (policy) so this agent may run automations. Configure may show a read-only Enabled / Disabled mirror with a link back into this panel. |
| **New automation** | Create a definition — from a sample template, from **My templates**, or blank. |
| **Definition** | One saved automation (name, schedule, capabilities, sources, model, notify options). |
| **Template** | Prefill only — edit freely after save. |
| **Artifact** | Output of a run (draft post, channel summary, markdown digest, and similar). |
| **Approve** | Mark a draft ready for outbound publish when the workflow requires it. |
| **Connection test** | Optional check for outbound credentials — you can enable an automation even if the test failed; fix credentials when a run or post errors. |

## Enable and run (any automation)

Use this path for every definition — whether you started from a sample or from a blank form.

**1. Open Automation**

In Starter Agent chat, choose **Automation** in the header. Confirm you are signed in as the agent owner.

**2. Turn on the master switch**

Use **Enable automation** on the panel when you are ready for this agent to run jobs. Configure may show the same state as read-only.

**3. Create with New automation**

Tap **New automation** → pick a **built-in** sample, a **My templates** entry, or start blank. Templates only prefill fields; change anything after save.

**4. Bind sources, model, and schedule**

Attach the sources your workflow needs (for example a launch feed or JEV handoff), choose model settings the form offers, set a schedule or **Draft** (manual), then **Test run** if available.

**5. Enable the definition**

Turn the individual automation **on**. Watch **job history** and **artifacts**. Approve or edit drafts before publish when the workflow asks for it. You can share artifacts to another agent you own when that action is available.

***

## Sample templates (examples to learn from)

These three built-ins are the first public how-to set — useful examples, not the full catalog. Other built-ins (for example Reply assistant or Founder daily ops) may already appear in the product before they get their own deep guide sections. Treat each section below as “one way to start,” then reshape the definition for your own workflow.

### Channel pulse

**Example job:** On a rhythm (for example every few hours), check your connected Boost channel for updates, milestones, and community chatter your agent can summarize.

**Typical outcome:** A digest-style note / mention list (poll / read path — not a public post by itself).

**How to try this sample:**

1. **New automation** → template **Channel pulse**.
2. Confirm the channel / source binding the form requires.
3. Set schedule (or manual draft + test run).
4. Enable and review **Channel check** style job results and summaries in history / artifacts.

In the product, tooltips describe scheduled checks that summarize what is new so you can act later (publish, reply, or digest elsewhere).

### Scheduled publish

**Example job:** When an **approved** draft exists, publish on the schedule (or rules) you configured — using your **connected social account** (bring-your-own connection). HeroBoost does not charge your prepaid balance for each post on this path.

**Typical outcome:** Post draft artifact → published reference after approve + successful outbound.

**How to try this sample:**

1. **New automation** → template **Scheduled publish**.
2. Connect outbound credentials the form lists; run **Connection test** if you want an early signal (optional — enable is not blocked on a failed test).
3. Produce or receive a **Post draft** artifact, then **Approve** when ready.
4. Enable the definition; confirm job history shows publish attempts and fix credentials if a run fails.

> [!WARNING]
>
> Publishing uses your connected social account. Keep credentials current. Errors surface on the next run or post if the connection is wrong.

### Research digest

**Example job:** Build a **daily markdown brief** in your workspace (research / summary style), typically on a daily schedule (for example morning local time when configured).

**Typical outcome:** Markdown brief artifact you can read in the workspace / artifact gallery — no outbound post required.

**How to try this sample:**

1. **New automation** → template **Research digest**.
2. Set sources and model the form asks for.
3. Choose schedule (daily) or test with a manual / run-now path if offered.
4. Enable and open the resulting brief from artifacts.

***

## Artifacts, sharing, and Configure

* **Artifacts** collect outputs from runs — open, edit drafts, approve when needed.
* **Share** to another agent you own stays inside your hero account (not public Explore visibility).
* **Configure** may show a short Automation status block — treat the **chat Automation panel** as the place to edit deeply.

## Related

* [Starter Agent overview](https://docs.heroboost.me/guides/starter-agent/overview.md)
* [JEV](https://docs.heroboost.me/guides/starter-agent/jev.md) — evaluation handoffs into automation
* [Slide](https://docs.heroboost.me/guides/starter-agent/apps/slide.md) — decks are separate from Automation schedules (Slide generate is not scheduled through Automation in the current light path); see also [Apps overview](https://docs.heroboost.me/guides/starter-agent/apps/overview.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.