Two ways to run it. Option A (recommended): write plain English in a Prompt column — works exactly like Claygent, impossible to break. Option B: write the prompt directly inside the Body — fine, as long as you follow four formatting rules every time.
| # | TCompany Name | 🔗Website | TPrompt | {}3P API Writer | ƒOutput |
|---|---|---|---|---|---|
| 1 | Brightline Labs | brightlinelabs.com | Write one sentence starting with "target"… | 200 · Success | Target the VP of Operations at Brightline… |
| 2 | Northgate HVAC | northgatehvac.com | Write one sentence starting with "target"… | 200 · Success | Target the owner-operator at Northgate… |
| 3 | Cobalt Analytics | cobaltanalytics.io | Write one sentence starting with "target"… | queued… | |
| 4 | Harborview Media | harborview.media | |||
| 5 | Fernwell Goods | fernwell.co |
| # | TCompany Name | TPrompt | {}3P API Writer |
|---|---|---|---|
| 1 | Brightline Labs | Write one sentence starting with "target" describing… | 200 · Success |
| 2 | Northgate HVAC | Write one sentence starting with "target" describing… | 200 · Success |
| 3 | Cobalt Analytics | Write one sentence starting with "target" describing… | queued… |
| 4 | Harborview Media | ||
| 5 | Fernwell Goods | ||
| 6 | Juniper & Co. |
Method, Endpoint and Account: identical to Option A above — only the Body differs. Spacing the JSON out across lines is fine; the only Enter key that breaks things is one inside your prompt text.
/ — they drop in as blue chips. Don't hand-type {{Column Name}} as text./.The API answers with its full technical envelope — IDs, model info, token counts. The sentence you asked for lives in one field: choices → 0 → message → content.
Click any cell in the 3P API column to open the response, find content, hover it and hit Add as column. Name it Output. That's it — done once, it fills for every row, and your table shows just the clean sentence from then on.
Clay doesn't mark a brand-new column's cells as "stale," so a normal run skips them all and the column just sits there blank. It's not broken — it needs one forced run.
Click the ▾ on the 3P API column header → Run column → Force run all. You'll know it worked when you see:
Status Code: 200 ✓ + text in your Output columnThe old failure: prompt text lived inside the JSON, so every quote mark and line break had to obey JSON escaping rules — and Clay un-escapes one layer before sending, which is why hand-typed bodies kept dying with Failed to parse body input. In this setup your prompt travels as data: the Prompt chip is wrapped in Clay's escaping function under the hood, so it's escaped perfectly, automatically, on every row — no human ever types inside the JSON, same reason Claygent's prompt box never breaks. (Live-verified: a prompt containing double quotes and line breaks came back 200 with clean output.) Option B works too — but there the prose sits inside the JSON, so the rules (single quotes, no Enter, chips via /) are on you every edit. That's the whole trade.