Hey Simon (simonand.co) yeah, this one’s a common headache. what’s worked for me is breaking the output into smaller batches before writing to clay. you can use limit/offset in your API step or split the dataset person-by-person to stay under 200kb. another trick is writing larger JSON results into text storage (like google sheets or notion) and then just reference it in clay.