Skip to main content

Get Support
Have a question? Let's get you an answer!

How Do I...? Troubleshooting Code & Webhooks Developer Zone

Other Help Resources
Wait, there's more! Check out these Community sourced spaces for additional resources.

Zapier Help Center Hire an Expert

Learning Resources
All of our best learning resources can be found here.

Featured Articles Show & Tell Zapier's products AI Hub Zapier Tools Hub

Share your knowledge
Give back to the Community by sharing your automation wins and helping to answer questions.

Share your success See unanswered questions User Groups

Other Learning Resources
Some of our favorite additional ways to upskill your Zapier knowledge.

Zapier Learn Zapier Blog Zapier Webinars

Product Updates
Check out what is new and upcoming with Zapier with our regular product updates.

Product Updates

Early Access Program
Want to join Early Access? Learn more here.

Question

Monday.com ZAP not picking up mirrored column values

  • November 25, 2025
  • 4 replies
  • 20 views
Y

We have been running this ZAP everyday for the past 4+months

today the zap is not picking the values from columns that mirrored from other boards in Monday.com or formula values that are duplicated to numeric columns via autoboost

 

Also GMT offset appearsto have changed as well, achieved via Formatter in ZAPier

 

Monday.com claim there have been no changes in the past 24hrs as has ZAPier so WTF???

 

Any ideas

The error you're encountering likely stems from the use of dynamic fields in your SMS message that are not being populated correctly from the previous step. Specifically, the placeholders like {{315078165__event__lookup_mktsd0et}} and {{315078165__event__mirror_1}} may not have valid data passed from the previous step, leading to an incomplete or invalid message format.

4 replies

moid-space
  • moid-space
  • New
  • November 25, 2025

Those dynamic fields are coming in empty, so Zapier can’t build the SMS. Re, test the Monday trigger with a fresh item and remap the fields. If they still don’t show up, use a Get Item by ID step, it reliably pulls mirrored/formula values.

Troy Tessalone
Zapier Orchestrator & Solution Partner
Forum|alt.badge.img+14
  • Troy TessaloneZapier Orchestrator & Solution Partner
  • Zapier Orchestrator & Solution Partner
  • November 25, 2025

Hi ​@YPD 

Help links for using Monday in Zaps: https://zapier.com/apps/monday/integrations#help

 

Things to check/try:

  • For live Zap Runs, check the DATA IN/OUT for each step to help you trace the data flow and troubleshoot
  • Check if the Zap is triggering before those Monday Board Column values are populated
  • Check the app status pages for recent/ongoing incidents that may be impacting the Zap Runs

 

If you need to hire help, there is a directory of Zapier Partners: https://zapier.com/partnerdirectory

⚡ Troy Tessalone - AutomationAce.com | Platinum Authorized Zapier Solution Partner | #1 Zapier Community Contributor
Y
  • YPDBeginner
  • Author
  • Beginner
  • November 26, 2025

as this was running before for months, there has to have been an application update by eitjer ZAPier or Monday.com

 

I shouldn't need to buy support to fix a problem introduced by the vendor

SamB
Community Manager
Forum|alt.badge.img+11
  • SamBCommunity Manager
  • Community Manager
  • November 26, 2025

Hi there ​@YPD 👋

Sorry to hear that your Zap has suddenly stopped working. I’ve checked on this end and couldn’t see any changed made to the Monday.com app integration on November 24th or 25th that would have caused this.

There was an incident on Monday.com’s end on the November 25th though, so I wonder if that might have interfered with the mirrored fields being updated with values before the Zap was triggered. If that’s the case, then that might be why Monday.com didn’t send any values in the Event Lookup Mktsd0Et and Event Mirror 1 fields and caused the SMS action to error. 

Do you think that might have been the case, or is the Zap still failing to see any values in those fields despite the incident being resolved?

Terms & ConditionsAccessibility statement