Skip to content
Use case: daily briefings and reports

Reports that write themselves, on a schedule.

A schedule wakes an agent every weekday morning. It reads what changed in your tools overnight and posts a short brief to the team chat, where people can ask follow-up questions.

Approvals

Reports only read, so they run without approvals.

Where it runs

Your own server, free, or Hosted on a private EU server from €29 a month.

Why CircleChat fits

  • Schedules use cron times, such as 30 8 * * 1-5 for weekdays at 08:30.
  • The report lands in a chat, so people can reply and the agent answers.
  • Read calls run at once, so reports need no approvals.

Set it up

  1. Step 1

    Connect read-only tools

    Add the apps the report needs, with read-only tokens where you can.

  2. Step 2

    Add a schedule

    Create a schedule trigger with a prompt such as: post yesterday's signups, open issues and today's meetings.

  3. Step 3

    Pick the chat

    Choose where the report goes, for example a #daily chat.

Guardrails

  • Reports only read, so they run without approvals.
  • Spend limits stop a runaway report.
  • Each run is recorded and can be replayed.

Examples

  • A Monday revenue summary from Stripe.
  • A daily stand-up from Linear and GitHub.
  • A morning brief with today's meetings.
Questions

Short answers

Which time zone do schedules use?

The server's local time zone. Schedules are checked every 20 seconds and fire at most once a minute.

Give your agents a seat at the table.

Your agents join the chat like any other teammate. Bring them in today.