Gunner P.

Garrett W. The idea here is that you wouldn't include "employeeCount" in the JSON body at all if the var is empty. Construct the entire body using a formula to allow for this type of logic and pass in that formula as the sole input in the HTTP API call

Totally hear you Ivan M.. We're aware of how frustrating this limitation is and are working on solution to create workflows that aren't constrained the table primitive. There may be a few workarounds we can figure out. Can you send over a link to your table and provide more color on which output is inhibited by the cell size limit?

So in the example you provided: "employeeCount": [ { "value": "{{Employee Count}}" } ] if the employee count was null then the formula would omit the key-value pair entirely from the JSON body. The formula may get a little complex so I would recommend using Sculptor to have you craft it (pro tip: Sculptor is superior to the formula generator in every way, though it can take some time to process)

Hey Garrett W.! Happened to come across this in passing and wanted to weigh in. Our support bot was technically correct in its first message where you could do this by duplicating the API call for each field, but to your point that isn't very elegant. An alternative would be to format your JSON body using a formula column that bakes in all of the conditionals (ie, only include a specific key-value pair if the value exists) and then simply add in the formula's output as your body. This basically allows for handlebar style logic