Action / Business automation and AI evaluation
Draft a recurring business review Action
Draft a recurring business review Action in Proforma. Make Data retrieval and reporting inspectable, then review cadence and release before scheduling.
Business operations lead
Bring this question into Chat
Your starting prompt.
Draft an Action for [recurring business review] that reads [approved Data] and prepares [report structure]. Keep retrieval, definitions and AI summarization explicit, with source dates, missing-data handling and run logs. Propose [cadence and timezone], reviewers and destination, but keep the Action unscheduled. Inspect existing Actions before creating one. Do not publish, activate a trigger or send a report until the runtime, release authority and destination are reviewed.
Copy this starting point, then replace the placeholders with your own inputs.
Method and review
Keep the assumptions visible.
Define inputs, outputs, permissions and failure conditions before implementing an Action. Evaluate AI against representative labeled examples and retain human approval for consequential steps.
For this task, check
The owner should verify retrieval and definitions, then separately approve the production deployment and intended delivery route.
Before you begin
- Permission to author an Action against approved Data
- Configured Action runtime and AI provider if summarization is used
- Release review before any schedule or external delivery
Repeat execution requires a configured Action. Agree the scope and authority before any external changes or messages.
Synthetic illustrative example
See the method in practice.
Synthetic input. Illustrative output checked locally; this is not a live Proforma run or customer result. Draft weekly report content only. Proposed cadence: Monday 09:00 America/Los_Angeles; owner review and destination are unconfirmed.
These invented records explain the method. They are not a recorded Proforma run.
| Report measure | Prior week | Current week | Source status |
|---|---|---|---|
| Revenue USD | 900 | 1000 | Defined Model; 30 Sep |
| Contribution USD | 300 | 280 | Defined Model; 30 Sep |
| Qualified accounts | 10 | Unknown | Definition missing |
| Proposed report section | Illustrative content | Required review |
|---|---|---|
| Revenue | $1,000; 11.1% increase | Confirm period and definition |
| Contribution | $280; -6.7% change | Explain margin drivers |
| Qualified accounts | Unavailable; definition missing | Resolve before reporting |
Method
Draft an Action that retrieves the approved Models, calculates period changes and prepares a reviewable report. Any AI summary should use these retrieved facts and retain source dates. Missing measures remain unavailable.
What the result tells you
The Action remains a proposed, unscheduled design. No report was generated by a Proforma execution or sent. Runtime configuration, exact deployment approval and destination authority are prerequisites for release.
Take the next step
Make it your investigation.
Copy the prompt above, create or open your Workspace, and paste it into Chat. Add the inputs you have permission to use and adapt the assumptions with your agent.
Start exploringYour prompt is carried by copy and paste. Signing up does not submit it or start this work automatically.
Or start with your own agent
The setup prompt includes this public task. Your agent will help you connect when needed and use the access you approve.