Dan V.

Hey Natalie thank you for the quick response, makes total sense

I'm thinking about Diana, who started Monday (thanks again for recommending her)!

Hey Natalie! Sound interesting. Is this for people who want to break into GTM Engineering or also people who have newly made that their title, too?

thanks, yes

Just my 2 cents it's maybe worth considering that other clients might find this titling change for readability's sake confusing if they're looking to similarly have fields named an exact way to pipe to other providers, maybe that's an edge case problem that's outweighed by the larger benefit of simplifying JSON titles for most users, though

Thank you Smit! That makes perfect sense. Hmm, I think maybe the Salesloft issue was unrelated to something on Clay's end and this stuck out as the likely cause to me but is concidental. I appreciate your prompt help!

https://app.clay.com/workspaces/502632/workbooks/wb_0t6xp9u7v2CnTsqdDrZ/tables/t_0t6xp9uBYECFNgNbpV6/views/gv_0t6xp9uzqi9uo9TpyZc thank you

This is going in circles a bit, would appreciate human support

I've already done that for step 1 and plan on doing step two. However this seems like a recent change that is specific to Claygent, not OpenAI's model. The same problem happens when I use Anthropic. Seems to be on your end

Hi, the prompt is very long, so here's the relevant bit in the prompt where I tell it how to format the JSON fields. { "Personalized_content_01": "subject line 1", "Personalized_content_02": "full email body 1 including signoff", "Personalized_content_03": "subject line 2", "Personalized_content_04": "full email body 2 including signoff", "Personalized_content_05": "subject line 3", "Personalized_content_06": "full email body 3 including signoff", "Personalized_content_07": "full email body 4 including signoff (RE: uses subject from Touch 3)", "Personalized_content_08": "subject line 5", "Personalized_content_09": "full email body 5 including signoff" } And then I define the field titles in outputs