Here is the corrected version:
I’ve been trying to use Make for about 3 weeks to post and update items from Recruit CRM into Webflow. I decided to stop because nothing was working. Now, I’m using Integrately and can create and update the CMS items from Recruit CRM. However, when I make a change, the data is pulled into Webflow and the item is updated but not published. My idea is to publish the items using Make. I created a scenario that watches for events on the CMS items, and those that change will be published. This works, but when I launched the scenarios live, it consumed all the operations in less than a minute.
blueprint (2).json (5.0 KB)
Hi,
This works, but when I launched the scenarios live, it consumed all the operations in less than a minute.
This probably happened because it listens for all events, not just those specified for your task.
If you can change when the webhook is triggered on Webflow’s side, that’s the way to go.
If not, set up a filter between modules to process only the events you want- you will save 1 operation per unnecessary execution.
In any case, each trigger will cost you 1 operation- so setting it up properly on Webflow side is crucial. You can learn more here.
Well right now is just listening changes on the live items on webflow but I don’t know what is a change for on an item for webflow hahaha, because I didn’t make 1.000 changes in an item in 1 minute that is imposible and the only set that i can do is that watch events – changes in an item.
When an item is published, Webflow sends a webhook call to your trigger module, which tells Webflow to publish it again, and then Webflow sends a webhook call to your trigger module, which tells Webflow to publish it again, and then Webflow sends a webhook call to your trigger module, which tells Webflow to publish it again, and then Webflow sends a webhook call to your trigger module, which tells Webflow to publish it again, and then Webflow sends a webhook call to your trigger module, which tells Webflow to publish it again, and then Webflow sends a webhook call to your trigger module, which tells Webflow to publish it again, and then Webflow sends a webhook call to your trigger module, which tells Webflow to publish it again, and then Webflow sends a webhook call to your trigger module, which tells Webflow to publish it again, and then Webflow sends a webhook call to your trigger module, which tells Webflow to publish it again, and then Webflow sends a webhook call to your trigger module, which tells Webflow to publish it again, and then Webflow sends…
You see how your 1000 operations get used up in a minute now? Each scenario run is 2 operations, so it only needed 500 loops to use the entire quota.
The issue is a circular event feedback loop - your scenario causes an action to be made that causes Webflow to re-trigger your scenario.
To avoid this, you need to uncheck the “listen to” CMS-related events in the Webflow connection itself.
Hope this helps! Let me know if there are any further questions or issues.
— @samliew
P.S.: Did you know, the concepts of about 70% of questions asked on this forum are already covered in the Make Academy. Investing some effort into it will save you lots of time and frustration using Make later!
