auto optimize recipe requested API fields based on utilization?
when building an integration it is certainly possible to pull in too much data, but while building the connections I dont want to limit my options so its common for me to pull the full field set. It would be nice if the recipe could auto detect the fields that are used in subsequent steps and only request for that data when a recipe is running. This would allow the API calls to be as lean as possible but not require the developer to track every field manually.
Arlen Thurber
auto optimize recipe requested API fields based on utilization?
when building an integration it is certainly possible to pull in too much data, but while building the connections I dont want to limit my options so its common for me to pull the full field set. It would be nice if the recipe could auto detect the fields that are used in subsequent steps and only request for that data when a recipe is running. This would allow the API calls to be as lean as possible but not require the developer to track every field manually.
is there a feature that does this currently?