Schedule a Weekly Report

The classic first assignment: a report that shows up every Monday morning without anyone assembling it. This guide uses a sales pipeline report as the example, but the shape works for any recurring summary — support volume, campaign performance, sprint status.

1. Connect the data source. Open Customize → Integrations in the Workspace scope and connect the system that holds your data — for a pipeline report, your CRM. OAuth integrations redirect you to the provider to authorize; API-key integrations take a pasted credential.

2. Pick or create the agent. Your personal agent can own the report, or create a dedicated one (New Agent, name it, give it a personality that matches the audience — “concise, numbers-first, flags risks early”).

3. Add the assignment. On the agent’s page, open Assignments and choose Add Assignment. Name it, then write the Instructions: what data to pull, how to analyze it, and what the deliverable looks like. Be explicit about the output — for example, “deliver a document with a summary table, the top five at-risk deals, and week-over-week changes.” The AI-assist button can draft this from a sentence or two.

   A complete set of instructions for the pipeline example might read:

   Every Monday morning, pull all open opportunities from Salesforce that changed in the last seven days. Summarize the pipeline by stage with week-over-week movement, list the top five at-risk deals with a short reason each is at risk, and flag any deal whose close date slipped. Deliver a document titled with the week’s date: a summary table up top, then one short paragraph per at-risk deal.

4. Set the schedule. In the Schedule section, choose Weekly, pick the day and time, and confirm the timezone (it defaults to yours).

5. Test it with Run now. Save the assignment, then press Run now and watch the session. You’ll see the agent query the integration, reason through the data, and produce the report. If the output isn’t right, refine the instructions and run again — the schedule doesn’t start counting against you while you iterate.

6. Let it recur. From now on the report runs on schedule. Each run is a session you can audit, and each report lands as a work product. If the agent hits a problem — expired credentials, missing data — it escalates to your Inbox rather than silently skipping a week.

Variations

The connect-describe-schedule shape carries well beyond a Monday pipeline report. A few riffs:

• Daily standup digest. Connect GitHub or Linear, set a Daily schedule for early morning, and ask for a short summary of what merged, what moved, and what looks stuck — a two-minute read in place of a status meeting.
• Monthly board pack. Set a Monthly schedule (the “last day of month” option fits here) and have the agent assemble a longer document from Salesforce and Stripe: revenue, pipeline, and the month’s notable wins and losses.
• Support-volume summary. Connect Zendesk or Intercom on a Weekly schedule and ask for ticket volume by category, escalations, and the themes behind the week’s hardest conversations.
• Sprint recap every two weeks. The Custom cadence handles “every 2 weeks on Tuesday” — point it at Jira or Linear and time it to land the morning after the sprint closes.

If the workspace’s Slack integration is connected, any of these can end with “post the summary to the team channel” — once connected, Slack’s tools are in the agent’s toolkit like any other integration’s. The full set of cadences is covered in schedules, webhooks, and triggers.