When a custom field is created for non-mandatory customer input and that field is linked with a Zap in Zapier, if the customer chooses not to input any data, trafft automatically sends a “/“ in the hook to zapier. If the zap is set to trigger when there is text output in the custom field, the Zap falsely triggers because of the “/“ in the output value field from traft. The only workaround I have found is to add a condition to the Zap to exclude “/“ from the input which works, although if the customer for any reason included a “/“ in their response, the Zap would not trigger. Removing the “/“ from the output field in the webhook from Trafft and leaving it empty “no data” would be the ideal solution.