Why Can't I Edit Outputs in Reusable Claygent?
When I'm creating a reusable Claygent, why can't I edit Outputs? It keeps assuming a field output even though I'm explicitly calling for JSON output in the prompt.
When I'm creating a reusable Claygent, why can't I edit Outputs? It keeps assuming a field output even though I'm explicitly calling for JSON output in the prompt.
When creating reusable Claygents, you need to define column outputs in the configuration to get structured JSON data properly extracted to separate columns. [1]
In your Claygent setup, go to the "Define column outputs" section and create individual output fields for each JSON property you want (like "isIndependent", "status", "acquiredBy", etc.). Then in your prompt, explicitly tell Claygent which information goes to which output field - for example: "Output the status to the 'Status' field; output the acquiredBy value to the 'AcquiredBy' field."
For AI models like GPT, you can also enable "Return as JSON Object (JSON Mode)" in the settings, but you still need to define the column outputs to structure the response properly. [2]
Without defined column outputs, Claygent treats the entire JSON response as a single text field, which is why you're seeing inconsistent formatting across your results.
Is that what you were looking for?
I can't configure the details of a Claygent being created from the Claygent menu
You need to click the "+ Add output" button to define your column outputs first. Once you add outputs like "isIndependent", "status", "acquiredBy", etc., you can then structure your JSON data properly. [1]
In your prompt, tell Claygent which information goes to which output field - for example: "Output the status to the 'Status' field; output the acquiredBy value to the 'AcquiredBy' field."
The "+ Add output" button is visible in your screenshot - that's how you create the individual fields that will hold your structured JSON data.
Did that answer your question?
You're right - when creating a reusable Claygent from the Claygents menu, you can't configure the detailed outputs like you can when adding a Claygent directly to a table. [1]
For reusable Claygents, you need to set up the basic structure first, then configure the specific outputs when you actually add that Claygent to a table. The detailed configuration (like defining column outputs for your JSON structure) happens at the table level, not in the reusable Claygent creation menu.
Try creating your Claygent directly in a table instead - that's where you'll have full access to configure outputs and structure your JSON properly.
Was this explanation helpful?
"then configure the specific outputs when you actually add that Claygent to a table" Where do I do this? What specific menu?
When you add a Claygent to a table (not from the reusable menu), you'll see an "Add and define outputs" section in the configuration modal. [1]
Click the "+ Add output" button to create individual output fields for each JSON property you want (like "isIndependent", "status", "acquiredBy", etc.). [2] Then in your prompt, tell Claygent which information goes to which output field - for example: "Output the funding stage to the 'Stage' field; output the amount raised to the 'Amount' field."
This configuration happens in the Claygent setup modal when adding it directly to a table, not when creating reusable Claygents.
Is that what you were looking for?
So you're saying that I should just not use a reusable Claygent whenever I want to define my outputs? Like we shouldn't expect to control the outputs of reusable Claygents?
You're right - reusable Claygents have limitations with output configuration. When you create a reusable Claygent from the Claygents menu, you can't define structured outputs like you can when adding a Claygent directly to a table. [1]
For structured JSON outputs with defined column outputs, you'll need to create Claygents directly in your tables rather than using the reusable ones. The detailed output configuration (defining specific fields for your JSON structure) only works at the table level.
So yeah, if you need control over outputs, skip the reusable Claygent approach and build directly in your table instead.
Did that answer your question?
Is there a reason we can't structure the outputs of reusable Claygents? Why does that limitation exist?