Trouble Integrating My Website Data With Monday.com

[joeroot]

Hi everyone, I’m currently managing a restaurant-related website that features Texas Roadhouse menu updates, reviews, and customer inquiries. I’ve been trying to integrate my website’s form submissions and content updates with Monday.com so I can track everything in one place — for example, storing new review submissions, coupon requests, and menu update alerts directly into a Monday board. The idea is to automate the workflow and reduce manual data entry. However, I’ve been running into several technical issues with the integration setup.

I started by using the built-in Monday.com API and tried sending data from my website’s backend (built on Node.js) to my Monday board through a simple POST request to the GraphQL endpoint. The request works fine sometimes, but other times it returns inconsistent errors like “Invalid Column ID” or “Null field value”, even though I’m passing the same payload each time. When it fails, the response code is 200, but the body contains partial errors, so it’s difficult to debug.

Another problem I’m facing is with automation timing. I’ve set up automations to trigger whenever a new item is created — for example, to send an email notification to my team when someone submits feedback from the website. However, the automation only works intermittently. Sometimes it triggers instantly, but other times there’s a delay of several minutes or no trigger at all. I’ve checked my Monday.com plan limits and API rate caps, and everything seems within bounds.

I also noticed that when sending larger payloads (for example, a full restaurant menu update with several fields), the request often times out or truncates part of the data. I tried reducing the payload size by batching the data, but that created duplicate items in the Monday board. I’m wondering if there’s a recommended way to handle large inserts into Monday.com from an external website, or if I should be using a middleware like Zapier or Make (Integromat) instead of sending data directly via the API.

Another odd behavior is that the status columns and dropdown fields on my board don’t always map correctly. For example, when my API tries to set a status to “Published,” Monday.com sometimes leaves it blank or defaults to the first option in the column. I’ve verified that the exact label matches, but it seems like there’s a mismatch between the column settings and what the API expects.

Has anyone else faced similar issues integrating their website data directly with Monday.com? I’d love some advice on how to handle unstable API responses, automation delays, and large data syncs more efficiently. My goal is to have a reliable system where my website automatically pushes all new content updates, form submissions, and leads into Monday.com without manual intervention. Any configuration or best practice tips would be hugely appreciated! Sorry for the long post

[joeroot]

@joeroot

Hi everyone, I’m currently managing a restaurant-related website that features Texas Roadhouse menu updates, reviews, and customer inquiries. I’ve been trying to integrate my website’s form submissions and content updates with Monday .com so I can track everything in one place — for example, storing new review submissions, coupon requests, and menu update alerts directly into a Monday board. The idea is to automate the workflow and reduce manual data entry. However, I’ve been running into several technical issues with the integration setup.

I started by using the built-in Monday. com API and tried sending data from my website’s backend (built on Node.js) to my Monday board through a simple POST request to the GraphQL endpoint. The request works fine sometimes, but other times it returns inconsistent errors like “Invalid Column ID” or “Null field value”, even though I’m passing the same payload each time. When it fails, the response code is 200, but the body contains partial errors, so it’s difficult to debug.

Another problem I’m facing is with automation timing. I’ve set up automations to trigger whenever a new item is created — for example, to send an email notification to my team when someone submits feedback from the website. However, the automation only works intermittently. Sometimes it triggers instantly, but other times there’s a delay of several minutes or no trigger at all. I’ve checked my Monday. com plan limits and API rate caps, and everything seems within bounds.

I also noticed that when sending larger payloads (for example, a full restaurant menu update with several fields), the request often times out or truncates part of the data. I tried reducing the payload size by batching the data, but that created duplicate items in the Monday board. You can check out my website as well. I’m wondering if there’s a recommended way to handle large inserts into Monday. com from an external website, or if I should be using a middleware like Zapier or Make (Integromat) instead of sending data directly via the API.

Another odd behavior is that the status columns and dropdown fields on my board don’t always map correctly. For example, when my API tries to set a status to “Published,” Monday. com sometimes leaves it blank or defaults to the first option in the column. I’ve verified that the exact label matches, but it seems like there’s a mismatch between the column settings and what the API expects.

Has anyone else faced similar issues integrating their website data directly with Monday. com? I’d love some advice on how to handle unstable API responses, automation delays, and large data syncs more efficiently. My goal is to have a reliable system where my website automatically pushes all new content updates, form submissions, and leads into Monday. com without manual intervention. Any configuration or best practice tips would be hugely appreciated!

Is there anyone who can help me?

[dmitry_noliam (Dmitry)]

Hey @joeroot ,

I’d say most of what you’re seeing can’t be diagnosed cleanly without checking the actual setup — especially the board structure, column IDs, and the exact mutation you’re sending. monday’s API is very sensitive to mismatches between what the board expects and what the payload delivers, so even one incorrect or outdated column ID can cause intermittent “Invalid Column ID” or “Null field value” errors. That’s usually the first thing I’d verify.

For the API part, I’d double-check:

• That all column IDs come directly from the API (not from the UI label)

• That column_values is being stringified correctly

• That your backend isn’t sending fields the board doesn’t currently support

  (If the board schema changed at some point, this can cause exactly the random partial errors you’re seeing.)

Without the actual payload it’s hard to pinpoint, but this is the area where 90% of integration issues happen.

Regarding the automations:

Automations in monday are not guaranteed to fire in real-time. Small delays are normal, especially when the account has multiple automations running in parallel or when the item is being updated very quickly after creation. If a trigger sometimes doesn’t fire at all, it’s usually due to recipe conditions or timing overlaps during item creation.

If the notifications are mission-critical, I’d consider using webhooks rather than relying only on in-account automations.

For the large payloads:

Batching is correct in principle, but if the board doesn’t have a stable unique identifier (like an external ID), retries can easily create duplicates. Adding such a field usually stabilizes the flow.

Overall, I’d say that I lack the full understanding of your operations as to: What exactly do you do in monday.com and what is handled where.

If you’d like we can jump on a call to discuss the overall setup and maybe there are simpler/other ways of solving your use case with a better success rate/flow.

Feel free to reach out: dmitry.rasin@noliam.com