Claymation
Creative Clay workflows (Claymation)
Prompt patterns, HTTP APIs, and the weird-but-working plays GTMes actually steal.
Read the sourceClaymation — Alex LindahlClaymation ↗Alex Lindahl writes Claymation as a GTM Engineer at Clay: workflows, prompt patterns, and the unglamorous API tricks that make a table feel like a product. The through-line is creativity over prompts-as-magic — commercial judgment on what is worth automating, then a small workflow that proves it.
Typical Claymation moves: MX-record checks to protect deliverability, HTTP API columns that turn any docs page into a Clay integration, Claygent research that returns structured fields instead of a blob, and copy experiments you can A/B on 50 rows before you spend credits at volume.
Steal the editorial standard, not just the templates. If a play cannot be explained in a few steps and credited back to a live table, it is a thread, not a playbook.
The loop
- Prototype in a 25–50 row table before touching production credits.
- Prefer HTTP API / webhook columns over waiting for a native integration.
- Force Claygent to return named fields (product, signal, opener) — never a paragraph.
- Instrument deliverability (MX, catch-all, warmed inboxes) as columns, not folklore.
- Publish the working version with the source table so other GTMes can fork it.
Featured from a public write-up. Read the original at Claymation — Alex Lindahl. Author: Alex Lindahl · LinkedIn · Site.