Spreadsheet to automation

Attach the file you already have & Chip reads it itself: the spreadsheet becomes a typed table, & one more sentence turns that table into an automation that runs without you.

Use case

Here's our contract spreadsheet, can you get it into the system?

The spreadsheet came attached as a CSV, nothing more.

What Chip did

Chip opened the file. With the columns in front of it, it worked out which columns are required, which one identifies a row (so a later re-import updates instead of duplicating), which columns are dates & amounts written the local way & which text column is really a fixed set of choices. It showed that mapping before writing anything, then asked the one question the file could not answer, where a guess would silently mangle data:

Chip: Two rows have an end date before their start date and three have no owner. Import them as-is, or hold them back?

Answer: Import them, I'll fix those two. The missing owners are ex-employees, leave blank.

What got built

Inside the existing service contracts space:

• A Contracts table. One row per contract, typed: dates are dates, amounts are numbers, status is a dropdown. Keyed on the reference, so a later re-import updates matching rows instead of duplicating them.
• Every row, cleaned & loaded in one go.
• A Contracts list, sorted by expiry date, with search & filters.
• A note on the table saying the spreadsheet is no longer the source of truth & what the amounts are in.

Chip checked the row count against the file.

Then the automation

With the table in place, the automation was one more sentence:

When a contract is 30 days from ending, email the account owner. Again at 7 days.

Chip built it as a daily job over the same table: every morning at 07:00 it finds the contracts ending in 30 or 7 days & emails the account owner, skipping any it has already warned for that window. It rehearsed the job with sending switched off, then switched it on. The full story of that build is Contract renewal alerts.

How it runs now. The team works from the table & the list. Every morning the automation reads the same table & emails whoever needs a nudge. Send an updated file later & matching rows update instead of duplicating; the automation picks the changes up on its next run.

Try it

Attach your own CSV to the request and paste:

Here's our contract spreadsheet, can you get it into the system?

Swap "contract" for whatever the file holds. Chip shows you how it read each column before writing anything & only asks about rows it cannot safely guess. Then say what should happen on top of it:

When a contract is 30 days from ending, email the account owner. Again at 7 days.