Google Sheets that fill in as things happen

A spreadsheet is still the most common database in the world, and Google Sheets in MadMax treats it as one. Workflows append rows as things happen, read a range to make a decision or write a digest, overwrite an exact range when the numbers change, and clear a range before a refresh, all in A1 notation (Sheet1!A1:B10, or just Sheet1 for the whole sheet). AI steps sit in between to classify, enrich or summarize, and an approval can hold a bulk overwrite until a buyer or a manager says yes. There are no Sheets triggers, so a run starts from a form, a webhook, a schedule, an email or another connected app's event. For a keyed row another step looks up by id, a MadMax data store is often the better fit, and Sheets is where you put the view people open. Describe it in plain English and MadMax builds the workflow, runs the scoring on a real submission, and previews the exact row it would append before it writes anything.

What teams build

• A hosted form collects name, company and the free-text "what are you looking for", an AI classify step labels the lead hot, warm or cold from the answer, append_row adds the row with the label and a timestamp, and an if branch texts the rep when the label is hot.
• A Monday 8 a.m. schedule runs read_range on Metrics!A1:F60, an AI summarize step writes five lines on what moved and what did not, and a send email step delivers it to the team so no one opens the sheet unless the digest says to.
• A webhook receives a supplier's new price list, a reshape step filters to the SKUs you stock, an approval emails the buyer the count and the five largest changes with one-click approve or reject, and on approve clear_range wipes Prices!A2:C500 before update_cell writes the new rows into place.

How it connects

Google Sheets connects with a service account rather than a Google sign-in. Create one in Google Cloud, download its JSON key, and paste two values from it into Settings → connectors → Google Sheets: the client_email and the private_key PEM block (an optional delegated user email is only for domain-wide delegation). Then share each spreadsheet with the service account's email, as you would with a colleague, because Sheets uses Drive's permission model. The key is encrypted at rest and resolved only inside your workspace at run time. See managing connections.

Related

• Form trigger
• Reshape step
• Approval step
• Data stores
• Managing connections