Sending and Automating Reports

Sending to a Client

A report for a client can have a schedule (weekly on a day, or monthly on a day from 1 to 28) and the people who get it. A report sent to a client is client email, so a person must approve it:

• Someone whose role allows approving reports presses Approve. They approve the schedule and the recipients together, as they are at that moment.
• If the schedule, the recipients, or the client changes, the approval no longer counts. The report shows Needs your approval and is not sent until someone approves again.
• Each send runs as the person who approved it, so it never shows more than they may see.
• Taking the approval back (Take Back Approval) stops the report going out.

Sending by email uses your company's own Email Sending. Until that is part of your account, you can preview and download reports, and Send says that sending is not on yet. Nothing is sent.

In Workflows and with Your AI Assistant

Workflows can use five steps: See the reports (action reports.list), Add a report (action reports.create), Change a report (action reports.update), Run a report (action reports.run), and Send a report (action reports.send). A run in a workflow tells the workflow only how many blocks there were and how many were not available, never the report's data. A scheduled run uses the view of the person who approved the send, or the person who built the report.

Your own AI assistant can read, build, and run reports through its connection, as the person who approved the connection and never with more access than that person has. It cannot approve a report, send one, or remove one.

The Actions

• Approve a client send (action core.reports.approve), take the approval back (action core.reports.unapprove), and send (action core.reports.send). All three are a person's own: AI agents and API keys cannot use them.