What is the best way to take a webhook response and pass it into a prompt for another column, if the response is bigger than 8kb (assuming that’s the max?) are there any good strategies or patterns for this?
The payload size limit for webhooks is 100KB, not 8KB. For large webhook responses that need to be passed to prompts in other columns, consider these strategies: • Extract key data: Parse the webhook response and extract only the essential fields needed for your prompt • Chunk the data: Break large responses into smaller segments and process them across multiple rows or columns • Use JSON parsing: Structure your webhook data efficiently and reference specific nested values rather than the entire payload • Filter at source: Configure your webhook sender to only include necessary data fields If you need further help with JSON formatting or parsing issues, please share your JSON structure so we can troubleshoot further.
The data is under 100kb, but when it is passed to a prompt it seems to be unable to load it in (as the prompts fail). table: https://app.clay.com/workspaces/414592/workbooks/wb_0sz6o8rKDEKcvtWGVhN/tables/t_0sz6of3c4wMcMuWNfJx/views/gv_0sz6of4Wfk99CYhzfsQ
Hey Jimmy, Thanks so much for reaching out - we're so excited you're using webhooks and Claygent in Clay! To answer your question, what I'd recommend is to first use a formula to intake your list of events and parse out only the relevant information for the Claygent model. This should allow you to reduce the data size into something that is processable by the model. I've taken a look and the fields I'd recommend keeping are those like Chat Body and Participant. To achieve this, you should add a formula column and use our formula generator to explain in natural language what you are after and the appropriate inputs. The system should then be able to generate a formula that has the output you need. Let me know how this goes and if you run into any issues!
What is the maximum size of text that can be piped into the prompt? In size or characters is fine
Hey Jimmy - great question: When Claygent references data from another column, it's subject to Clay's cell size limits: ** Action column cell size limit: 200kB (approximately 200,000 characters) ** Formula column cell size limit: 8kB ** *Source column cell size limit: 100kB (e.g., webhook payloads) I believe the issue here is with the lists on some of your webhook pulls being too large. The formula method should be able to chop this down. For context, the Claygent model is able to process different amounts of input data depending on the use case.
Hope this helps!
Thank you! So this means I still can post the entire payload to the webhook, right? And then use a formula to chop it down once it’s in the webhook column? It sounds like the webhook payload can be 100kb but the input to another cell prompt can only be 8kb but please correct me if I’m wrong
Hey Jimmy! Your first intuition is correct, you should be able to post the entire payload to the webhook. For the 8kb limit, this is referring to what the "Formula Text" would be, not necessarily it's inputs or references to other columns. This means that after you post your <100kb Webhook the formula should be able to chop it down appropriately. Hope this helps and if you run into any issues let us know!
But the issue is that I could not put the events list into the prompt of another column, correct? Which would be the input to the column, wouldn’t it?
Hey Jimmy! I believe the issue was with the model itself rather than hard cell limits. Essentially we allowed the input into the cell, indicating that it was under the hard limit for the action, but the model was unable to parse that amount of data in this use case. It's something we are thinking about internally and constantly making improvements on. That being said, the formula should still be able to function well to help with your build. Let me know how it goes!
Now I have run to cell constraints with 8kb. even just passing in the chat and the sender seems to be too large.
Hey! Since you’re running into the 8KB cell limit with just the chat and sender fields, you’ll want to slim it down even further before it’s passed into the prompt. The best way is to use a Formula column to extract only the specific parts you need—like trimming long messages, removing metadata, or keeping just names and message content. If it’s a list of messages, you can also limit the number of entries or only pull in the last few. The limit applies to the final result of the formula, not the full webhook column—so you can still keep the full payload in your source column and work from there. Let me know if you’d like help building that formula.
This thread was picked up by our in-app web widget and will no longer sync to Slack. If you are the original poster, you can continue this conversation by logging into https://app.clay.com and clicking "Support" in the sidebar. If you're not the original poster and require help from support, please post in 02 Support.
.png){kind=logo}
