Hey All!
Was looking for some info on how HTTP Callouts via the new flow beta offering work in Scheduled Flows. I am under the impression that, while this option is available regardless of flow type, this will not work in scheduled flows for any batch size larger than 1. For instance, if I have 100 Account records that fit my scheduled flow entry criteria, and I write my scheduled flow in a format to be automatically bulkified by Flow builder (writing the flow as though I am handling just 1 singular record), the Flow will balk and identify the callouts as though they are part of an apex queueable (throwing a flow error). Is there a shared agreement that any batch of HTTP callouts should not be handled by the new HTTP Callouts offering in Flow?
Zack Terry (Fast Slow Motion) 
Forum Ambassador
Hi @Davis Johnson,
I found this snippet from Salesforce Time (thanks to @Yumi Ibrahimzade) that may be helpful:
If you want to use this action in a schedule-triggered flow, add a pause element to wait before calling the action. Otherwise, you might get this error:
"Callout failed for invocable action ExchangeRatesAPI.ExchangeRatesAPI. Can't perform callout when resuming a flow or inside an Apex Queueable. Place the callout to External Services invocable actions before pausing a flow or scheduling an Apex queueable. For more information, contact your Salesforce administrator."
