Report Scheduler
Put your reporting on autopilot. Schedule recurring prompts to have your AI generate and email insights right when you need them.
The Report Scheduler automates recurring AI-generated reports. At each scheduled time, the system sends your prompt to the chosen agent, collects the response, and emails it to the address you set, completely on autopilot.
Navigate to Report Scheduler
- 1. Go to Report Scheduler in the sidebar. This page lists all your existing schedulers with their status, next run time, and last run time.
- 2. Click Create Scheduler in the top-right corner.
Configure the Scheduler
Fill in the following fields:
| Field | Description |
|---|---|
| Schedule Name * | A recognizable name, e.g. "Weekly Sales Summary". |
| Description | Optional context about what this report covers. |
| Agent * | The agent that generates the report. |
| Prompt Message * | The exact message sent to the agent on each run. |
| Email * | Where the report is delivered. Your account email is pre-filled. |
| Schedule * | Use the visual builder to set frequency: yearly, monthly, weekly, or daily. |
| Start Date / End Date * | The active date range (interpreted in GMT+7). |
Click Create Schedule. The scheduler is active immediately.
Write your prompt the same way you'd ask the agent in chat. If your agent has database tools, ask it to query live data. If it has a knowledge base, ask it to summarize documents.
Run a Test
Click the Play icon on the scheduler's row to trigger an immediate test run, without waiting for the next scheduled time. The result is emailed to the configured address.
Always test before the scheduler runs automatically. A test run is the fastest way to catch prompt issues before they appear in a live report.
Monitor Results
Click the Results (document) icon on any scheduler row to open its run history. Each entry shows the run time, status, and the full report content the agent generated.
Statuses
Running on schedule.
Exists but won't run until reactivated.
Has reached its end date.
The last run encountered an error. Check the results view for details.
Editing and Deleting
Use the Edit (pencil) icon to update any field. Use the Delete (trash) icon to permanently remove a scheduler.
Deleting a scheduler does not affect its past results.
Webhook Integration
The Webhook field (under Advanced settings in the create/edit form) lets you automatically forward the completed report to any external system — n8n workflows, Slack bots, internal dashboards, or any HTTP endpoint.
Flow
The webhook fires after the report is generated, not before. The full sequence is:
- Scheduler triggers at the configured time.
- The agent runs the prompt and generates the report.
- The report is emailed to the configured address.
- The scheduler sends an HTTP POST request to your webhook URL with the report content as the body.
Request Payload
The scheduler POSTs a JSON body with a single key:
| Key | Type | Description |
|---|---|---|
| report_result | string | The full report text generated by the agent. |
Example:
| Key | Value |
|---|---|
report_result | "Q1 revenue: $1.2M. Top product: Plan A at 42% of sales. Churn rate: 3.1%." |
Setup
Open Create Schedule or Edit Schedule, scroll to the bottom, and click Advanced settings.
| Field | Notes |
|---|---|
| Webhook URL | Must be a publicly accessible POST endpoint. No authentication supported. |
| Method | Always HTTP POST — GET is not supported. |
In n8n, add a Webhook trigger node, set the method to POST, and use the report_result field from the JSON body in your workflow.
The webhook URL must be reachable from the internet without any authentication headers or redirects.
Delivery Status
Every run records the webhook outcome. Go to Results → View Detail to inspect it:
| Field | Description |
|---|---|
| Status | Delivered or Failed. |
| HTTP Status Code | The code your endpoint returned (e.g. 200, 500). |
| Error Message | Shown if the call failed. |
| Sent At | Timestamp of the webhook call. |
A webhook failure does not affect the report itself. The report is still generated and emailed normally — the webhook is a post-processing step only.