Build the report before choosing delivery
- 1Choose the evidence
Select project tasks, financial records, company knowledge or an authorized connected resource. Specify the reporting period and what the report must explain.
- 2Prepare the report
Add the analysis or work-product step. Distinguish recorded facts, planned amounts and missing evidence. A daily report can cover a sprint; the sending date and reporting period are separate.
- 3Add the delivery action
Choose the action for the intended audience. Link the report or preceding analysis as its content source. A generated file alone is not an email delivery step.
- 4Configure approvals and timing
Review the action’s recipient scope and approval requirement. Set the launch mode in Start workflow or Schedule & runs and save the configuration.
- 5Start and verify
Use Start if the agent is paused. Check the next scheduled run, then inspect the delivery step result and your mailbox after the first run.
Use Company for one cross-project report
For one combined overview, open Agent Center → Work areas → Company, choose the saved agent and select all or specific projects and processes. Build the report in this company map and set its schedule in Start. All includes future sources; Select includes only the checked sources.
Completed company files appear in the agent’s private company results. This scope does not add an email or team-chat delivery action. To send through connected mail or a project chat, use the corresponding authorized project workflow and review its delivery permissions.
Use the right recipient action
| Audience | How recipients are determined |
|---|---|
| Workflow owner | The Collty report-to-owner action sends to the configured workflow owner account. It does not require selecting a particular project task. |
| Company owner | The company-owner notification action resolves the owner from the authorized company context. |
| Task team members | Notify assignees by email resolves recipients from the selected tasks’ current assignments and prepares recipient-specific task information. It is not a broadcast to every company member. |
| Other authorized recipients through connected mail | Use the available Gmail or other MCP mail tool. Select its account and bind real recipient addresses and required message fields. External sends follow that action’s approval policy. |
| Team chat or shared client chat | Use the corresponding project chat action. A chat notification and an email are distinct delivery actions. |
Daily means every day; workdays is a separate choice
In Schedule & runs, Every day includes weekends. Monday to Friday excludes Saturday and Sunday. Every week lets you select a weekday, or several days, and the launch time. Once on a date and At regular intervals are different modes.
Use Add time for several launches on each selected day, for example 09:00, 13:00 and 17:00. Remove a time with its × button. All launch times use the selected time zone. The summary lists all times and the next eligible run. Existing schedules retain their original single time.
Start enables execution; Pause retains the configuration and prevents further scheduled work. Save persists edits and does not replace Start or Pause. An unfinished project workflow continues instead of starting a duplicate at the next launch. Record workflows can still discover new source records while existing records await input or approval.
A daily report can run even when no particular task starts that day. Add task-status conditions only when the workflow should actually depend on those conditions.
Choose One project workflow for a scheduled report that does not depend on a particular task. Each matching task and Delegated tasks only start separate task-based work.
System reports use a shared presentation
Collty system agent reports use one shared email layout for existing and newly created agents. The subject is the agent’s name followed by report, for example Superior report. The report heading inside the email can still explain the content.
Dates and reporting periods use compact readable text instead of oversized numerical metric tiles. The template organizes supported metrics, labelled facts, sections and task cards consistently.
Mail sent through an external MCP account follows that tool’s content and signature settings. It does not automatically inherit the Collty system report template. Specify the intended outgoing content and signature before approving it.
If a report did not arrive
- 1Check whether a run exists
Open Schedule & runs → Current work and recent runs. If there is no run, check the active state, cadence, time zone, next run and any launch condition.
- 2Check the delivery step
A completed analysis or saved document does not prove that an email was sent. Open the send step for its confirmed result or the reason it is waiting.
- 3Resolve the precise blocker
Check approval, recipient source, connected-account authorization, AI Credits and any unavailable evidence or provider. Paused agents do not send scheduled reports.
- 4Check the mailbox
Search for the agent-name report subject and inspect spam or filtering. A successful provider send is different from a guarantee of inbox delivery.
- 5Retry with awareness of prior results
Inspect previous sends before a manual retry to avoid duplicate mail. Stop cannot undo an email already sent.