Spec the automation of a manual recurring report: sources, transformations, edge cases like late data, and the human checkpoint worth keeping.
Spec automating this manual report: {{report}} (what it shows, who gets it, how it's built today, how long it takes, where the data comes from).
Document: sources and access method per data element, the transformation steps currently in someone's head (extract them into rules — including the judgment calls: how are refunds handled? which timezone?), edge cases that will break naive automation (late-arriving data, month boundaries, renamed categories, zero-activity periods), the delivery mechanism and schedule, the validation the automation runs on itself before sending (totals reconcile, row counts plausible), and the one human checkpoint worth keeping vs full auto. Estimate build effort honestly against time saved.
Fields like {{ this }} are placeholders — replace them with your own details, or let Aria ask you for them.
This prompt runs with Aria connected to your email, files, CRM and 40+ other services — and you can schedule it to run automatically.
Start Free WeekPull structured data out of messy text — emails, PDFs pastes, reports — into a clean table, with con...
Get the right Excel or Google Sheets formula for your layout — explained part by part, with a worked...
Get a structured first read of pasted data: observations with the numbers cited, trends vs noise sep...
Turn open-ended survey answers into themes and quotes.
Pick the best chart type for what you want to show.
Write or optimise a SQL query from a plain-English description of the data and the question — with t...