Claymation
Creative Clay workflows
HTTP APIs, MX checks, named Claygent fields. Steal the table, not the thread.
The loop
- 01Prototype on 25–50 rowsProve the play before you touch production credits.
- 02Prefer HTTP API over waitingAny docs page can be a Clay column. Don’t wait for native.
- 03Force Claygent to return fieldsProduct, signal, opener — never a paragraph blob.
- 04Instrument deliverability as columnsMX, catch-all, warmed inboxes. Not folklore.
- 05Publish the working tableIf it can’t be forked, it is a thread, not a playbook.
Most Clay writeups stop at the prompt. Lindahl’s newsletter is a running log of tables other GTM Engineers can actually fork. The interesting part is the surrounding system: named output fields so the next column has something typed to bind to, HTTP API as the default when Clay has no native, and credit math that treats a 5,000-row hallucination as a budget failure, not a research win.
That editorial layer is why the workbook is the unit of work. Lindahl is a GTM Engineer at Clay writing for peers who already live in the product — which columns to instrument, when to stop iterating, how to hand a working table to someone else without a 40-minute loom. The live workbook is the artifact. The thread is just the receipt.
