AutoReport.to

Prompt placeholders

AI instructions

Shortcuts you insert into your report instructions. They help the AI use the right data and the right dates—no manual copy-paste each time you run a report.

How to use placeholders

  1. Open Create Report or edit an existing report, then select the AI instructions step on the canvas.
  2. Under Placeholders, click any token to insert it at the cursor—or type the same text exactly (including the double braces).
  3. Write your instructions as usual. Tokens like {{commits}} tell the AI which data to focus on; Run & dates tokens are replaced with real calendar dates when the report runs.
  4. Save the report. The next manual or scheduled run will use your instructions with placeholders filled in automatically.
Create a report

Placeholder reference

Search by name, token, or integration. The same list appears as clickable chips in the AI instructions step when you pick a data source.

Run & dates

{{report_run_date}}

Report run date

The calendar date when your report actually runs—useful for titles or “generated on” lines.

{{work_week_monday}}

Work week — Monday

Monday of the completed Monday–Friday period AutoReport uses for your timesheet-style week range.

{{work_week_friday}}

Work week — Friday

Friday of the same week as Monday—use both together, e.g. “Week of {{work_week_monday}} – {{work_week_friday}}”.

GitHub

{{commits}}

Commits

Commit messages and metadata from the configured repo branch; use for change logs and engineering summaries.

{{issues}}

Issues

Issue titles and bodies from the configured GitHub issues query.

{{pr_titles}}

Pull request titles

Pull request titles for release-style or review summaries.

Stripe

{{new_mrr}}

New MRR

Stripe-derived new monthly recurring revenue context when available in the fetch payload.

{{churn_rate}}

Churn rate

Churn-related metrics from the Stripe data bundle when present.

Clerk

{{users}}

Users

User listing or activity from Clerk for admin or growth summaries.

{{active_count}}

Active count

Count of active users or sessions depending on the configured Clerk resource.

WhatsApp

{{whatsapp_messages}}

WhatsApp messages

Messages from the linked chat (see Data Context: `data.messages`). The worker adds `data.combinedTextChronological`: each bubble is prefixed with `[message id="…" timestamp="…"]` so the model can tie IDs to text; empty/media-only bubbles are explicit placeholders.

Slack

{{thread_summary}}

Thread summary

Channel or DM history context for Slack-based reports.

Linear

{{issues}}

Issues

Linear issues for sprint or bug-focused summaries.

{{cycle_summary}}

Cycle summary

Cycle-related context when fetching Linear cycles.

Notion

{{pages}}

Pages

Notion page content included in the fetch payload.

{{databases}}

Databases

Notion database rows or views when configured.

Discord

{{messages}}

Messages

Discord messages from the configured channel or scope.

{{channels}}

Channels

Channel listing or metadata when included in the fetch.