# Fix Scenario Integration with Monday **URL:** \ **Category:** Hire Help\ **Tags:** error, webhooks\ **Created:** [February 25, 2026, 1:23pm UTC](https://community.make.com/t/fix-scenario-integration-with-monday/104304 "2026-02-25T13:23:53Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![Adi1](https://avatars.discourse-cdn.com/v4/letter/a/ecb155/32.png) [@Adi1](https://community.make.com/u/Adi1)\ **Post date:** [February 25, 2026, 1:23pm UTC](https://community.make.com/t/fix-scenario-integration-with-monday/104304/1 "2026-02-25T13:23:53Z")
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](http://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 ---
**Author:** ![Pathfinder\_Automate](https://dub1.discourse-cdn.com/flex013/user_avatar/community.make.com/pathfinder_automate/32/92144_2.png) [@Pathfinder\_Automate](https://community.make.com/u/Pathfinder_Automate)\ **Post date:** [February 25, 2026, 1:35pm UTC](https://community.make.com/t/fix-scenario-integration-with-monday/104304/3 "2026-02-25T13:35:12Z")
Hello @Adi1 , welcome to [make.com](http://make.com/) community, I have worked and have experience with [Make.com](http://make.com/) and l will love to collaborate with you on this you can schedule a call [Here](https://calendly.com/taiwo-pathfinderautomationsolutions/30min) and you can checkout my upwork profile [Here](https://www.upwork.com/freelancers/~01446d60f782215efa), for my pastworks and certifications ---
**Author:** ![Greatness\_Solutions](https://dub1.discourse-cdn.com/flex013/user_avatar/community.make.com/greatness_solutions/32/93374_2.png) [@Greatness\_Solutions](https://community.make.com/u/Greatness_Solutions)\ **Post date:** [February 25, 2026, 1:38pm UTC](https://community.make.com/t/fix-scenario-integration-with-monday/104304/4 "2026-02-25T13:38:08Z")
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](http://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](https://calendly.com/philipadeniji655/) ---
**Author:** ![Gabriel\_Akinola](https://dub1.discourse-cdn.com/flex013/user_avatar/community.make.com/gabriel_akinola/32/83825_2.png) [@Gabriel\_Akinola](https://community.make.com/u/Gabriel_Akinola)\ **Post date:** [February 25, 2026, 1:43pm UTC](https://community.make.com/t/fix-scenario-integration-with-monday/104304/5 "2026-02-25T13:43:47Z")
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](http://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](mailto:fopefoluwaakinola@gmail.com) Looking forward to helping you get it running again. ---
**Author:** ![Deborah1](https://dub1.discourse-cdn.com/flex013/user_avatar/community.make.com/deborah1/32/76780_2.png) [@Deborah1](https://community.make.com/u/Deborah1)\ **Post date:** [February 25, 2026, 2:07pm UTC](https://community.make.com/t/fix-scenario-integration-with-monday/104304/6 "2026-02-25T14:07:56Z")
Hi Adi1, welcome to the community 👋 The error is happening because the scenario is still referencing a deleted column ID in [Monday.com](http://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 ---
**Author:** ![Farhan\_Ahmed](https://avatars.discourse-cdn.com/v4/letter/f/b5a626/32.png) [@Farhan\_Ahmed](https://community.make.com/u/Farhan_Ahmed)\ **Post date:** [February 25, 2026, 2:19pm UTC](https://community.make.com/t/fix-scenario-integration-with-monday/104304/7 "2026-02-25T14:19:36Z")
> [@Adi1](#): > > 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](http://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 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](http://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](http://Make.com) workflows and working with [Monday.com](http://Monday.com) integrations, I’m confident I can get this scenario running successfully again. 📄 Check my profile:[https://www.upwork.com/freelancers/farhana401](https://www.upwork.com/freelancers/farhana401) 📞 Book a quick call:[Calendly - Automaxion](https://calendly.com/automaxion-meet) ---
**Author:** ![Folafoluwa\_Olaneye](https://dub1.discourse-cdn.com/flex013/user_avatar/community.make.com/folafoluwa_olaneye/32/91924_2.png) [@Folafoluwa\_Olaneye](https://community.make.com/u/Folafoluwa_Olaneye)\ **Post date:** [February 25, 2026, 3:40pm UTC](https://community.make.com/t/fix-scenario-integration-with-monday/104304/8 "2026-02-25T15:40:44Z")
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](mailto:folafoluwaolaneye@gmail.com) [folafoluwaolaneye@gmail.com](mailto:folafoluwaolaneye@gmail.com) Portfolio: View my past related automation works [here](https://mavin-collins.my.canva.site/flowedge-portfolio-website). Book a call: Schedule a Jobscope walkthrough session [here.](https://cal.com/folafoluwa-olaneye-osrofp/30min). (P.S: Adjust the time zone before booking) Or proceed via my Fiverr workspace: [http://www.fiverr.com/s/qD1jlXZ](http://www.fiverr.com/s/qD1jlXZ) Looking forward to hearing from you. Best regards, Folafoluwa Stephen Flowedge Digitals ---
**Author:** ![Sergey2](https://avatars.discourse-cdn.com/v4/letter/s/f14d63/32.png) [@Sergey2](https://community.make.com/u/Sergey2)\ **Post date:** [March 13, 2026, 2:19am UTC](https://community.make.com/t/fix-scenario-integration-with-monday/104304/9 "2026-03-13T02:19:15Z")
Hi, This looks like a targeted repair job, not a rebuild. In a 22-module scenario, the stale column ID can survive in mapped fields, filters, routers, or raw JSON payloads, so the main work is tracing every reference to connect\_boards4\_\_1, replacing it with the new column, and then running a safe end-to-end test. I can take this as a fixed cleanup task if you still need it. If you share whether that deleted column was used only inside Monday modules or also inside filters/functions, I can tell you the quickest path to get the scenario stable again. ---
**Author:** ![icq416597405](https://avatars.discourse-cdn.com/v4/letter/i/8dc957/32.png) [@icq416597405](https://community.make.com/u/icq416597405)\ **Post date:** [May 22, 2026, 8:27am UTC](https://community.make.com/t/fix-scenario-integration-with-monday/104304/10 "2026-05-22T08:27:50Z")
Hi, I can help with this kind of Make/Monday repair. The first paid slice can be very small: inspect the 22 modules, find every reference to the deleted `connect_boards4__1` column, map it to the current board column, and run a controlled test so the scenario is working again. I would also leave a short note with the old/new column mapping and any fragile module references, so this does not break silently next time a board column changes. If this is still open, share a screenshot/export of the failing module and the current Monday board column list, and I can scope the fix.