Hi, quick update…
I’ve been working with Zapier support over the last two weeks and we’ve made some progress in narrowing down the problem.
We’ve successfully bypassed the first placeholder data issue in step 1 (Find Data) and have changes triggered in Monday.com coming through to Zapier (viewable in Task History).
The second issue we have found after bypassing the first, is that the Monday.com v2 APIs are not passing through all the board fields when something changes on a particular pulse.
For example, our test case is that we have a Status and Email field on a board. When the Status changes to ‘Done’ on a pulse we want to send an email from Zapier to the email address in the Email field on that same pulse.
The issue is that when you change the status in Monday.com, the APIs only pass through the changed field along with a couple of core fields. However the email field is not passed at all.
The only way we have been able to make any of the other fields on the board get passed through is by changing the specific field directly. However, again, it only passed through the core fields plus the changed field. So in this example, there is no way to get the Email field value when the Status field value is what’s changed.
This is a limitation with how the APIs operate with Zapier and unfortunately there is no solution on the Zapier end. This needs to be fixed by Monday.com.
Ideally what should be happening is that anytime there is a change triggered on any field on a board, the APIs should pass through ALL the fields for the changed pulse to Zapier.
We’ll have to leave the Zapier integration for now and try again once Monday.com has made improvements to how the APIs integrates with Zapier.