# Network calls in workflow query handler

**URL:** <https://community.temporal.io/t/network-calls-in-workflow-query-handler/224>\
**Category:** Community Support\
**Created:** [July 19, 2020, 8:24pm UTC](https://community.temporal.io/t/network-calls-in-workflow-query-handler/224 "2020-07-19T20:24:08Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![pauldemarco](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/pauldemarco/32/19_2.png) [@pauldemarco](https://community.temporal.io/u/pauldemarco)\
**Post date:** [July 19, 2020, 8:24pm UTC](https://community.temporal.io/t/network-calls-in-workflow-query-handler/224/1 "2020-07-19T20:24:08Z")

</div>

Is it okay to reach out to external APIs and perform network calls from within a workflow Query Handler?

Follow-up question: does the query handler run within the workflow or activity worker process?

---

<div class="post-metadata">

**Author:** ![maxim](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/maxim/32/8_2.png) [@maxim](https://community.temporal.io/u/maxim)\
**Post date:** [July 19, 2020, 9:32pm UTC](https://community.temporal.io/t/network-calls-in-workflow-query-handler/224/2 "2020-07-19T21:32:13Z")

</div>

It is OK as the query handler is not allowed to mutate the workflow state. But the current implementation of the SDK doesn’t make it easy to pass external dependencies to the query handler.

One possibility to fix this is to allow running local activities from the query handler.