All articles
2 min read#agents#automation#recipes

Forty pages from one spreadsheet

The hard part of making forty link pages was never the pages. It was the forty conversations about what goes on them.

The shape of the job

Somebody already has the table: a column of names, a column of addresses they would like, a column of links, sometimes a photo URL. What they do not have is the will to open an editor forty times. An agent with that table and an API key does the whole run in a few minutes, and the interesting design question is not how to loop — it is what to do with the results.

Two shapes are possible. Either every stall gets its own account, provisional and unclaimed, and you send each owner a claim link so the page becomes theirs. Or all forty live on the organiser’s account, which keeps control central and means the organiser maintains them forever. The first is almost always right, and it is the reason claim links exist.

  1. Validate every row first, in one pass, with nothing created. Bad addresses and duplicate names surface as a list you can fix in the spreadsheet.
  2. Create one page per row, each with its own idempotency key built from the row — a re-run then repairs the failures and touches nothing else.
  3. Keep the claim link and the page address back in the table, next to the row they came from.
  4. Send each owner their two links, with one sentence saying what the claim link does.

What to put in the rows, and what not to

  • A label per link, written by the person, not generated: «Order bread» beats «Website» every time.
  • A photo URL when there is one. A page with a face or a product is a different page from one without.
  • One featured link per row at most, and only when the row actually has a main thing.
  • No invented bios. An empty bio is honest; a generated one reads like a generated one and the owner will feel it.

Where a batch run goes wrong

Rate limits are the first wall: without a key, ten pages a day from one address; with a key, ten an hour on that account, and ten pages per account for programs. A forty-row run therefore means forty accounts, paced — which is also the shape you want, because forty accounts is forty owners.

The second wall is silence. Pages nobody claims and nobody visits are unpublished after thirty days and removed after sixty. That is a feature for a run that fizzled and a disaster for one where the e-mails never went out. Send the claim links the same day you create the pages.

Read next