Analytics automation is software in which an analyst builds a data workflow by dragging ready-made steps onto a screen, without writing code. The workflow then runs again by itself, every day or every week. Typical steps are: pull the data, clean it, combine it, analyse it and send out the result. The screen on which the analyst arranges the steps is often called a workflow canvas.
Most of this work used to be done by hand in spreadsheets. An employee opened the same five files every Monday, copied columns, corrected spellings, ran the same formulas and emailed the result. It took hours each week, and one wrong paste could spoil the numbers.
Take, for example, an FMCG distributor in Lucknow. FMCG means fast-moving consumer goods, the everyday products such as soap, tea and biscuits that shops sell daily. The distributor supplies four brands to 2,500 shops across six districts. Every Monday, its sales manager wants to know which shops are about to run out of the best-selling items. The sales representatives can then visit those shops first.
The data comes from three places. Each brand's distributor management system exports the week's orders as a file. The distributor's accounting software exports each shop's unpaid dues. And a spreadsheet lists each shop's address and its sales representative.
The analyst builds one workflow with eight steps. The first steps read the three files through ready-made connectors. A cleaning step corrects shop names, so that "Gupta Kirana, Aliganj" and "GUPTA KIRANA ALIGANJ" become one shop. A join step matches each order to its shop and its sales representative. A formula step works out each shop's average weekly purchase of each item. A filter step keeps the shops that have bought less than half their usual amount for two weeks running. It also drops any shop that owes more than ₹20,000, because the distributor does not want to send more stock to a shop that has not paid. The last step writes a visit list for each sales representative, and copies the totals to the distributor's BI dashboard.
Building the workflow takes the analyst two days. After that, it runs every Monday at 6 a.m. and finishes in under five minutes. This week, it lists 140 shops. If a brand changes the format of its file, the analyst changes one step, not the whole job.
Some workflows also include steps that run statistics or forecasts. Others send the prepared data to statistical software for deeper analysis.
How is this different from a data engineer's ETL or ELT pipeline? Both move and clean data. A pipeline is code that engineers write and maintain for the whole company, and it loads the data warehouse. Analytics automation is built by an analyst, without code, to answer one team's question. It is also different from robotic process automation (RPA), which repeats a person's clicks on a screen instead of working on the data itself.