Skip to content
Closed
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -34,15 +34,15 @@
| **Monthly** | Runs on chosen dates each month | Monthly reports, regular maintenance |
| **Custom** | Runs on specific dates you select | One-off tasks or irregular schedules |

#### Advanced: cron expressions

Check warning on line 37 in build/agents/build-your-agent/agent-triggers/scheduled-triggers.mdx

View check run for this annotation

Mintlify / Mintlify Validation (relevanceai) - vale-spellcheck

build/agents/build-your-agent/agent-triggers/scheduled-triggers.mdx#L37

Did you really mean 'cron'?

For more precise control over scheduling, you can use **Cron expressions**. Relevance AI uses **AWS EventBridge cron format**, which requires **six fields**:

Check warning on line 39 in build/agents/build-your-agent/agent-triggers/scheduled-triggers.mdx

View check run for this annotation

Mintlify / Mintlify Validation (relevanceai) - vale-spellcheck

build/agents/build-your-agent/agent-triggers/scheduled-triggers.mdx#L39

Did you really mean 'Cron'?

Check warning on line 39 in build/agents/build-your-agent/agent-triggers/scheduled-triggers.mdx

View check run for this annotation

Mintlify / Mintlify Validation (relevanceai) - vale-spellcheck

build/agents/build-your-agent/agent-triggers/scheduled-triggers.mdx#L39

Did you really mean 'cron'?

```
minute hour day-of-month month day-of-week year
```

**Cron Expression Format:**

Check warning on line 45 in build/agents/build-your-agent/agent-triggers/scheduled-triggers.mdx

View check run for this annotation

Mintlify / Mintlify Validation (relevanceai) - vale-spellcheck

build/agents/build-your-agent/agent-triggers/scheduled-triggers.mdx#L45

Did you really mean 'Cron'?

| Field | Values | Wildcards |
| --- | --- | --- |
Expand All @@ -64,7 +64,7 @@
- `W` - nearest weekday
- `#` - nth occurrence of a day in a month

**Common Cron Expression Examples:**

Check warning on line 67 in build/agents/build-your-agent/agent-triggers/scheduled-triggers.mdx

View check run for this annotation

Mintlify / Mintlify Validation (relevanceai) - vale-spellcheck

build/agents/build-your-agent/agent-triggers/scheduled-triggers.mdx#L67

Did you really mean 'Cron'?

```
0 10 * * ? * # Every day at 10:00 AM
Expand All @@ -80,7 +80,7 @@
```

<Note>
AWS EventBridge cron expressions use 6 fields, unlike traditional Unix cron which uses 5 fields. Always include the year field, and use `?` for either day-of-month or day-of-week when specifying the other.

Check warning on line 83 in build/agents/build-your-agent/agent-triggers/scheduled-triggers.mdx

View check run for this annotation

Mintlify / Mintlify Validation (relevanceai) - vale-spellcheck

build/agents/build-your-agent/agent-triggers/scheduled-triggers.mdx#L83

Did you really mean 'cron'?

Check warning on line 83 in build/agents/build-your-agent/agent-triggers/scheduled-triggers.mdx

View check run for this annotation

Mintlify / Mintlify Validation (relevanceai) - vale-spellcheck

build/agents/build-your-agent/agent-triggers/scheduled-triggers.mdx#L83

Did you really mean 'cron'?
</Note>

### Tips
Expand All @@ -88,16 +88,20 @@
- **Start small**: Begin with one simple recurring task before setting up complex schedules
- **Test thoroughly**: Run your agent manually first to ensure it works as expected
- **Monitor initially**: Check the first few automated runs to confirm everything works correctly
- **Use cron for precision**: When you need exact timing control, use cron expressions instead of simple schedules

Check warning on line 91 in build/agents/build-your-agent/agent-triggers/scheduled-triggers.mdx

View check run for this annotation

Mintlify / Mintlify Validation (relevanceai) - vale-spellcheck

build/agents/build-your-agent/agent-triggers/scheduled-triggers.mdx#L91

Did you really mean 'cron'?

Check warning on line 91 in build/agents/build-your-agent/agent-triggers/scheduled-triggers.mdx

View check run for this annotation

Mintlify / Mintlify Validation (relevanceai) - vale-spellcheck

build/agents/build-your-agent/agent-triggers/scheduled-triggers.mdx#L91

Did you really mean 'cron'?

---

## Scheduled messages

![](/images/agent/scheduled-messages.png)

Check failure on line 97 in build/agents/build-your-agent/agent-triggers/scheduled-triggers.mdx

View workflow job for this annotation

GitHub Actions / Documentation Lint Checks

Image has no alt text — add a short description of what the image shows inside the brackets, e.g. ![The agent configuration panel](path). [technical: empty alt attribute detected in markdown image syntax ![](path)]

Scheduled messages let your Agent send messages at specific future times — follow-ups, reminders, check-ins, or any time-based outreach. You can edit or reschedule these messages directly in Task View.

<Info>
To view and manage all pending scheduled check-ins across your agents from a single place, use the [scheduled check-ins panel in Inventor](/build/invent/invent).
</Info>

### Setting up Scheduled Messages

1. Navigate to the **Build** page
Expand Down Expand Up @@ -125,7 +129,7 @@

#### Max daily Scheduled Triggers

Set a limit on how many scheduled actions your Agent can process in a single day. Leaving it at "No limit" means the Agent can schedule and send as many future messages as needed. If you want to control costs, manage system load, or prevent overactivity, you can set a specific maximum number.

Check warning on line 132 in build/agents/build-your-agent/agent-triggers/scheduled-triggers.mdx

View check run for this annotation

Mintlify / Mintlify Validation (relevanceai) - vale-spellcheck

build/agents/build-your-agent/agent-triggers/scheduled-triggers.mdx#L132

Did you really mean 'overactivity'?

#### Prevent Scheduled Messages from interrupting a Task

Expand Down
9 changes: 9 additions & 0 deletions build/invent/invent.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -36,7 +36,7 @@
Get a recommendation on tool vs. agent vs. workforce based on your use case.
</Card>
<Card title="Build and improve evals" icon="flask-vial" href="/build/agents/build-your-agent/evals">
Diagnoses errored logs and tools, explains why a run failed, and proposes how to fix it — so you can build stronger evals.

Check warning on line 39 in build/invent/invent.mdx

View check run for this annotation

Mintlify / Mintlify Validation (relevanceai) - vale-spellcheck

build/invent/invent.mdx#L39

Did you really mean 'errored'?

Check warning on line 39 in build/invent/invent.mdx

View check run for this annotation

Mintlify / Mintlify Validation (relevanceai) - vale-spellcheck

build/invent/invent.mdx#L39

Did you really mean 'evals'?
</Card>
<Card title="Log bugs to engineering" icon="bug-slash">
When Inventor hits a platform issue it can't fix, it logs a bug to our engineering team on your behalf.
Expand Down Expand Up @@ -122,7 +122,7 @@
## How to use Inventor

<div style={{ width:"100%",position:"relative","padding-top":"44%"}}>
<iframe src="https://app.supademo.com/embed/cmq65ouq340ajqm6u2uly8nst?embed_v=2" frameBorder="0" title="How to use Invent" allow="clipboard-write; fullscreen" webkitAllowFullscreen="true" mozAllowFullscreen="true" allowFullscreen style={{ position:"absolute",top:0,left:0,width:"100%",height:"100%",border:"3px solid #5E43CE",borderRadius:"10px" }} />

Check failure on line 125 in build/invent/invent.mdx

View workflow job for this annotation

GitHub Actions / Documentation Lint Checks

Supademo embed is missing rounded corners — use the standard embed snippet. [technical: borderRadius: '10px' missing from iframe style]

Check failure on line 125 in build/invent/invent.mdx

View workflow job for this annotation

GitHub Actions / Documentation Lint Checks

Supademo embed is missing the purple border — use the standard embed snippet. [technical: border: '3px solid #5E43CE' missing from iframe style]

Check failure on line 125 in build/invent/invent.mdx

View workflow job for this annotation

GitHub Actions / Documentation Lint Checks

Supademo embed isn't using the standard wrapper — replace it with the snippet from the style guide. [technical: paddingTop: '56.25%' missing from wrapper <div>]
</div>

<Warning>
Expand Down Expand Up @@ -216,6 +216,15 @@
<Tab title="Restore a version">
Ask Inventor to roll an asset back to an earlier version — for example, "Restore the previous version of this tool". Inventor copies that version into the current draft, leaving the live published version unchanged until you publish. This restores an earlier version of an existing asset; it doesn't recover one that's been deleted.
</Tab>
<Tab title="Scheduled check-ins">
Click the **clock icon** in the **Inventor** toolbar to open the scheduled check-ins panel. The panel lists all pending check-ins your agents have scheduled — up to 200 at a time — in one place. From there you can reschedule any check-in by editing its time, or cancel it entirely.

Previously there was no single place to see or manage pending check-ins across your agents. The scheduled check-ins panel gives you that view without having to open each agent individually.

<Info>
Scheduled check-ins is in early access and may not be available on all accounts.
</Info>
</Tab>
</Tabs>

## MCP vs Inventor
Expand Down
Loading