I have a zap that’s been running fine for a year now. It just creates an Item in Monday from a parsed message. This is in the Create Item - Set up Action section. I went today to edit the zap and all the fields are looking like this: why, please?
Best answer by christina.dView original
@paulruss! I wanted to pop in and see if the tips from my friends in support did the trick for you?
It looks like this was the last recommended step:
Keep us posted! 🤗
I should have spotted the correspondence between the unused custom fields and the newly available fields, Fixed now. But it might be worth contacting Monday.com - they still demonstrate the JSON custom fields on their site.
Actually, the Extra Fields mean those fields were removed from the Monday Board, not that those fields weren’t available from the Zap trigger step.
Thanks for letting us know that you were able to get your Zap working! When you say that Monday still demonstrate the JSON custom fields on their site, is that on a help page or when you’re in the app? I’d like to look into this so I can pass it along to the right team. Thanks!
When you see data that looks like that in your Zap - a number and the name of a field in double brackets - it means that the Zap can no longer find that field. The most obvious reason for this would be if the email template for the parser has been changed, if that hasn’t happened then it’ll need someone to take a closer look. If that’s the case, the best thing to do is to contact the Support Team using our Get Help Form. They’ll be able to dig into your Zap with you and hopefully get to the bottom of things.
But they do say :
Now, we support text updates for most columns, so you can simply type in the relevant info.
That said, some of the more advanced column types, like the Connect Boards or Dependency Columns, will require you to use the Column Values section. Those column types require a specific data structure in order to be filled with data.
But my post should be hopefully useful for others still using JSON to populate fields that now have direct access input
Hi - thanks for the answers.
Keep in mind that the zap is working still.
Those fields were JSON custom fields - nothing has been removed from the boards themselves. Either Zapier has broken/deprecated something in the api - or Monday.com have changed something their side. It must be a problem with Zapier as the JSON fields were I think never interrogated from Zapier previously: it was a one way data push?
Monday support just said ‘we dont support zapier - really handy!’. Unless I can find a solution I cant update those fields in Zapier.
Thanks for the extra context on this! If your current Zap is working, I would definitely make a copy of it and edit the copy so you don’t lose the working Zap.
Without seeing the whole Zap and its logs in the backend of our system, this is tricky to troubleshoot. The best thing to do is to contact the Support Team, who can take a closer look at this for you, you can do that using the Get Help form. Thanks!