Fix Scenario Integration with Monday

Hire a Pro Hire Help
,
1

I have an existing Make scenario that automates task creation in Monday. The scenario stopped working after a column was accidentally deleted from a Monday.com board.

The error message is: [200] This column ID doesn't exist for the board [Error Code: InvalidColumnIdException / Error Details: {"column_id":"connect_boards4__1"}]

The scenario includes approximately 22 modules. Most are working correctly, but one or more modules are still referencing the deleted column ID connect_boards4__1 which needs to be updated to the new column.

What I need:

  • Identify all modules referencing the old column ID

  • Update them to use the correct existing column

  • Test the scenario to confirm it runs successfully

1 Like
3

Hello @Adi1 , welcome to make.com community, I have worked and have experience with Make.com and l will love to collaborate with you on this you can schedule a call Here and you can checkout my upwork profile Here, for my pastworks and certifications

4

Hi @Adi1 , I’ve reviewed this and I understand the core issue you’re trying to solve.

I can help you design and implement a clean, reliable automation that fixes this without unnecessary rebuilding. I’ve worked on similar workflows involving Make.com , APIs, conditional logic, and production-grade error handling, and I can start immediately.

If it helps, I’m happy to do a quick review of your current setup and outline the exact fix before proceeding. You can jump on a short call with me here

5

Hi Adi,

I can help you fix this quickly.

From the error, your scenario is still referencing the deleted Monday column ID connect_boards4__1. In Make, this usually happens inside one or more Monday “Create/Update Item” modules, or inside mapped fields where the old column ID is hardcoded.

Here’s how I’ll handle it:

• Review the full 22-module scenario
• Identify every module referencing connect_boards4__1 (including mapped fields and JSON mappings)
• Replace it with the correct existing column ID
• Re-map the column properly to avoid future ID conflicts
• Run controlled tests to confirm the scenario executes successfully
• Deliver a fully working, tested automation

I’ve worked extensively with Make.com and Monday integrations, including fixing broken column mappings after structural board changes, so this is a straightforward repair.

If you can share:
– The scenario blueprint (export JSON)
– The Monday board ID
– The new column ID

I can resolve this fast.

You can reach me directly at: fopefoluwaakinola@gmail.com

Looking forward to helping you get it running again.

6

Hi Adi1, welcome to the community :waving_hand:

The error is happening because the scenario is still referencing a deleted column ID in Monday.com. With 22 modules, those references can exist in multiple places.

I can help identify all affected modules, update the mappings correctly, and test the scenario to ensure everything runs smoothly again.

Feel free to DM me so we can discuss the details and get this fixed quickly.+234 904 684 2148

7

I can help you resolve the issue with your Make scenario. It looks like the error is caused by a deleted column ID in Monday.com.

To fix this, I will:

  1. Identify all modules referencing the old column ID.

  2. Update them to use the correct existing column.

  3. Test the scenario to ensure it runs smoothly.

With my experience in troubleshooting Make.com workflows and working with Monday.com integrations, I’m confident I can get this scenario running successfully again.

:page_facing_up: Check my profile: https://www.upwork.com/freelancers/farhana401
:telephone_receiver: Book a quick call:Calendly - Automaxion

8

Hi @Ad1,

Welcome to the community.

This is a straightforward structural issue. When a column is deleted in Monday, its internal column ID is permanently removed, and any Make modules referencing that ID will fail even if a new column with the same name is created.

With a 22 module scenario, the fix usually involves:

• Auditing each Monday module for hardcoded column mappings

• Checking any Set Variable, JSON, or mapping fields where the old column ID may still be referenced

• Rebinding the affected fields to the new column ID

• Running controlled test executions to confirm stability

A few quick questions:

• Was the deleted column a Connect Boards type only, or are there other column types involved?

• Was the column recreated with the same structure and settings?

• Is this scenario triggered by webhook or scheduled polling?

I can quickly trace all references to connect_boards4__1, update them properly, and validate the full execution flow so nothing else breaks downstream.

You can reach me directly at: folafoluwaolaneye@gmail.com

folafoluwaolaneye@gmail.com

Portfolio: View my past related automation works here.

Book a call: Schedule a Jobscope walkthrough session here.. (P.S: Adjust the time zone before booking)

Or proceed via my Fiverr workspace:

http://www.fiverr.com/s/qD1jlXZ

Looking forward to hearing from you.

Best regards,

Folafoluwa Stephen

Flowedge Digitals