# Question about when a collection gets fetched

**URL:** <https://community.weweb.io/t/question-about-when-a-collection-gets-fetched/19587>\
**Category:** Ask us anything\
**Created:** [August 7, 2025, 10:45am UTC](https://community.weweb.io/t/question-about-when-a-collection-gets-fetched/19587 "2025-08-07T10:45:42Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![oli](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/oli/32/8397_2.png) [@oli](https://community.weweb.io/u/oli)\
**Post date:** [August 7, 2025, 10:45am UTC](https://community.weweb.io/t/question-about-when-a-collection-gets-fetched/19587/1 "2025-08-07T10:45:42Z")

</div>

Hi folks, unsure if this is a feature or a bug -

I’ve got a workflow that includes “fetch collection” block that is a REST API that is posting a webhook over to Zapier, with some information to trigger a Zap. The “fetch collection” is within a workflow that is started by clicking a button.

But I’ve noticed that the Zap is triggered on page load, before a user has triggered the workflow via the button, which implies that WeWeb is automatically “fetching” the collection before the user asks it to.

This isn’t how I would expect it to work, but can see why it might be expected if you’re assuming all collections on a page should be fetched on page load. So my question is - is this a bug, or working as intended?

(I’m open to alternative ways to trigger a Zap in the frontend too!)

---

<div class="post-metadata">

**Author:** ![Agustin\_Carozo](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/agustin_carozo/32/13231_2.png) [@Agustin\_Carozo](https://community.weweb.io/u/Agustin_Carozo)\
**Post date:** [August 8, 2025, 9:12pm UTC](https://community.weweb.io/t/question-about-when-a-collection-gets-fetched/19587/2 "2025-08-08T21:12:15Z")

</div>

Hi Oli 👋

I’m not sure I understand, how are you “Fetching“ a collection (API GET) that is writing to Zapier (API POST)?

Can you share a couple screenshots showcasing your workflows and app?

---

<div class="post-metadata">

**Author:** ![Broberto](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/broberto/32/5918_2.png) [@Broberto](https://community.weweb.io/u/Broberto)\
**Post date:** [August 9, 2025, 1:53pm UTC](https://community.weweb.io/t/question-about-when-a-collection-gets-fetched/19587/3 "2025-08-09T13:53:48Z")

</div>

Check out if you have fetch automatically enabled on your collection. It’s a little hidden, but if you have this enabled, it will fetch your collection on page load - given its data is used anywhere in the current page. Otherwise I’d look into whether you aren’t triggering it from somewhere without being aware of it.

---

<div class="post-metadata">

**Author:** ![oli](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/oli/32/8397_2.png) [@oli](https://community.weweb.io/u/oli)\
**Post date:** [August 11, 2025, 8:05am UTC](https://community.weweb.io/t/question-about-when-a-collection-gets-fetched/19587/4 "2025-08-11T08:05:18Z")

</div>

It doesn’t really make sense, I appreciate that! Here’s a screenshot of the collection, which is actually just posting data to Zapier (this is triggered within a workflow via a “Fetch collection” action.

 ![image](https://us1.discourse-cdn.com/flex016/uploads/weweb/original/2X/8/8fe66e3dd6bd8bce3231d3e25b1b1effc7ed8e87.png)

I think @Broberto’s suggestion is the correct answer - I just did some (fairly light) testing and it looks like if unselect “fetch automatically” it doesn’t trigger the Zap on page load, only via the workflow. So thank you!

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/weweb/original/2X/b/bee40a614c5b74fbef4e7bb6f73d022e2b8203e3.png) [@system](https://community.weweb.io/u/system)\
**Post date:** [October 21, 2025, 10:46am UTC](https://community.weweb.io/t/question-about-when-a-collection-gets-fetched/19587/5 "2025-10-21T10:46:33Z")

</div>

Closed on October 21, 2025, 10:46am UTC

This topic was automatically closed after 75 days. New replies are no longer allowed.
