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.

Pick or create the agent. Your personal agent can own the report. To give it to a dedicated agent instead, open Agents, choose New agent, and give it a Name. Choose Write it yourself, since this guide sets the assignment up by hand; the personality can be filled in or left empty.
Add the assignment. On the agent’s page, open the Assignments card and choose Add assignment. The assignment is created right away and opens on its own page as “New assignment.” Rename it in the title field, then fill in the Instructions tab: 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 in the editor’s toolbar can draft this from a sentence or two. Edits save as you make them; the header reads Saved once they land.

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.
Connect the data source. Under the assignment’s name, a line reads either Runs as you or Runs on a company account, and that decides where the CRM connection belongs. Your personal agent, like any agent you have not shared with the workspace, runs as you: connect your own Salesforce account in Account settings → Connections, or ask an admin to open the company’s account to private agents. An agent shared with the workspace runs on company accounts, which a workspace admin connects in Skills & integrations → Integrations. Either way, OAuth integrations redirect you to the provider to authorize, and API-key integrations take a pasted credential. To make sure every run loads Salesforce, add it under Integrations in the Options tab; when an account the assignment uses is missing, the assignment page lists it with a button that connects it.
Set the schedule. In the Schedule tab, check Run on a schedule, set Frequency to Weekly, pick the day under Days, and set the time. The timezone defaults to your browser’s.
Test it with Run now. Press Run now in the header. It opens the new session, where you can watch the agent query Salesforce, reason through the data, and produce the report. If the output isn’t right, refine the instructions and run again. Manual runs work even while the assignment’s automated triggers are paused, so you can iterate before the schedule is live.
Let it recur. From now on the report runs on schedule. Each run is a session you can audit, listed in the assignment’s History tab, and each report lands as a work product. If a scheduled run cannot start because an account it needs is missing, you get an Inbox item saying which one, instead of a week silently skipped.

Model, effort, and budget

The Options tab also holds Budget & effort, which sets three things for this assignment’s runs. Model picks the tier: Tactical is the default for execution work, Strategic brings deep reasoning to the hardest work, and Operational is the fastest and cheapest for light jobs. Effort runs from Low to Max. Session budget ($) caps what one run may spend; it is unset by default, and once you set it, a run that reaches it pauses. Leave any of the three on Default or blank and the value comes from the agent, workspace, or organization. These fields save together, with Save budget & effort.

A weekly pipeline summary rarely needs more than the defaults. A monthly board pack that reconciles several sources is where Strategic earns its cost.

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 frequency 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 agent can reach the workspace’s Slack connection, any of these can end with “post the summary to the team channel” — Slack’s tools sit in the agent’s toolkit like any other integration’s. The full set of cadences is covered in schedules, webhooks, and triggers.