Skip to content
Context docs

Recurring reports with automations

An automation runs an agent with the same instructions each time, either on a schedule or when something happens in another app. Each run is a task you can open, and the results are saved to Drive.

Run the job once as a normal task first. When the result is right, you know what the automation’s instructions should say. Otherwise you may only find out the instructions were wrong after five runs.

Schedule a report

  1. Go to Home > your workspace > Automations.
  2. Click Create automation. To pick the trigger first, open the arrow next to it and choose On a schedule, On a GitHub event or From another app. Give it a title, such as “Weekly sales summary”.
  3. Under Agent (“Who does the work”), choose the agent. The automation keeps the agent it was made with.
  4. Under Instructions, say what to do on each run. For example:

    Read the latest file in @Juniper Weekly Sales. Write a one-page summary of this week vs last week: total sales, top five products, and anything that moved more than 20%. Save it as a .docx in the same folder, named with today’s date.

  5. Click Add trigger and choose Schedule. You can run it every hour, every day, every weekday or every week, at a time and time zone you choose. Check the time zone, especially if your team is in several countries.
  6. Check Runs on and Runs as. Runs use a cloud sandbox unless you pick a paired machine, and they run with your access.
  7. Create it. It is on straight away, and each run appears under Runs.

If you already have a task you want to repeat, click + > Automations in the composer to send it later or on a schedule.

Writing instructions for a run you won’t watch

At 8 am on a Monday the agent can’t stop to ask you a question. Name the exact folder, file and format in the instructions. Put the date in the file name, such as “Sales summary 2026-11-02.docx”, so each week’s report is kept separately.

Open the first three runs from Runs and check them. If something is wrong, click Edit and fix the instructions. The Calendar view on the Automations page shows what runs when.

Other triggers

  • GitHub event runs when something happens in a repository. Pick the event and the repository. GitHub must be connected.
  • Another app runs when any service sends a web request. When you create it, you get an address and a secret key.

Pause or remove an automation

Automations use credits on every run. Click Pause on any you no longer need, or delete them.