Operations · Reports & digests
KPI Collection and Narrative Reporting
Starts when: Every Monday, with a monthly roll-up on the first business day
Free plan · Outcome verification included · You approve every connection
How it runs
Six stages, from the moment it starts to the checks that keep running afterwards.
It starts
Every Monday, with a monthly roll-up on the first business day
Awish plans it and asks for each app
The apps it needs are connected one at a time, with your permission, before anything runs.
It does the work
Exactly as the request below describes, across the connected apps.
It stops where a person should decide
Call out missing data and never hide a change in how a metric is defined.
It verifies the outcome
After each run, Awish checks that the task, approval or document reached its owner.
It keeps monitoring
Failures, silent failures and connection health are watched on every plan; anomalies, root cause and recommendations on Business.
The request it runs
This is what opens in chat when you use the template. Change any part of it before anything connects.
“Set up an automation that manages recurring KPI collection and narrative reporting. Run it every Monday at 9:00 AM and on the first business day of each month for the monthly roll-up. It should pull the defined KPIs, validate their freshness, compare them to targets and to the prior period, flag anomalies, generate a short narrative with the key drivers and the owner actions, and publish the report. Connect it with Google Sheets, Salesforce, Zendesk and Stripe. Call out missing data and never hide a change in how a metric is defined.”
- Google Sheets
- Salesforce
- Zendesk
- Stripe
Monitoring included
What Awish watches once this template is running.
- Outcome verificationEvery plan
- Silent-failure detectionEvery plan
- Connection healthEvery plan
- Hours saved and ROIEvery plan
- Anomaly detectionOn Business
- Root-cause explanationOn Business
- Recovery recommendationOn Business
Questions about this template
Can I change where it stops for approval?
Yes. Open the template in chat and say where you want it to stop. The plan updates before anything connects.
What if one of these apps is not connected yet?
Awish asks you to connect each app it needs, one at a time, before the workflow runs. You can decline any of them.
How does Awish know this workflow worked?
After each run it checks that the task, approval or document reached its owner, in the app where that should happen. If a run reports success but the result is missing, it flags a silent failure.
Run it on your own apps
It opens in chat with the request written. See the plan, approve each connection, and Awish verifies the outcome from the first run.
Free plan · No credit card required