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.

Hi,

Two days ago, my automations using the API Request function of Monday.com stopped working on multiple Zaps. I am getting a 500 Error; however, Monday.com indicates no outages AND these API requests were perfectly fine when I throw them into Monday.com’s developer sandbox.

The API Request is actually incredibly simple, and straight from one of Monday.com’s API examples. I am just finding the item ID by searching the name of the item.

query {
  boards (ids: xxx) {
    items_page (query_params: {rules: l{column_id: "name", compare_value: l"Test Project Ignore"], operator:contains_text}]}) {
      items {
        id
        name
      }
    }
  }
}

 

 

 

 

 

 

Any thoughts? I know 500 is usually indicative of an issue on Monday.com’s end, but the developer community over there seems to be just fine. Thanks so much for any advice.

 

Hi @Meatbagz 

If your Zaps are ON, then check the live Zap Runs here: https://zapier.com/app/history/

Check the DATA IN/OUT for each Zap step.

Check the LOGS tab to see the underlying API request/response to help you troubleshoot.

Thank you for the response @Troy Tessalone 

It is a fairly simple 500 status code. The requests/responses were fine for a couple months with daily usage. They have just started getting this response two days ago.

 

 

@Meatbagz 

Can you post screenshots showing the API Request info for the Zap Run with an error?

Data In

 

Data Out 1/4
Data Out 2/4
Data Out 3/4
Data Out 4/4

 

My apologies, I forgot to tag you @Troy Tessalone but no rush and thank you for the help.

@Meatbagz 

Looks like you need to escaped some of the query values.

Replace instances of XXX with your dynamic variables.

{
  "query": "query { boards(ids:  XXX]) { items_page(query_params: { rules:  { column_id: \"name\", compare_value:  \"XXX\"], operator: contains_text }] }) { items { id name } } } }"
}

 

Hi @Meatbagz 👋

Just came across this and wanted to check how things are going? Did Troy’s last reply here help to get that API Request sorted? 

If it did, we’d love to get it marked as the best answer here to better surface it to other folks that are running into similar issues. 

And if not and you’re still stuck at all just let us know - happy to lend a hand! 

@Troy Tessalone was (and is) extremely helpful but the ultimate answer was that Monday.com appears to have broken something with the 2024-10 API update. It is ultimately unclear to me if it is a Zapier or Monday.com issue, but rolling back the Monday.com API to 2024-07 fixes the issue. This is not a long term fix though, as that API will eventually be deprecated.. Me and several community members (including @Troy Tessalone ) discuss “fixing” the issue here: 

 

As a note - the non-escaped items were a temporary change when I was trying EVERYTHING to get this query to work. Troy is right that it was wrong, but it was not the core issue. I will mark him as the best answer.

 

@SamB 

Thanks for getting back to me @Meatbagz. Really appreciate you taking the time to share this detailed update! 🤗 And a big thank you to @Troy Tessalone for helping out in both threads! 🧡

If it’s not working with the more recent version of the Monday.com API but is with the old then I’d expect that it’s likely something that would need to be resolved on Monday.com’s end rather than Zapier’s. That said, I would recommend reaching out to our Support team to have this investigated further from our side.

I’m so glad you’ve been able to get a temporary fix in place for now. If there’s anything else we can assist with in the meantime please do reach back out to the Community! 🙂

Reply


Terms & Conditions