Have sent you a DM as well. Would love to help you debug your current CMS workflow and fix it to run reliably by adding error handling using Make. I run an automation studio called Automation Jinn where we help companies automate their processes and increase efficiency. I am Make advanced certified with a background in computer science so quite comfortable in integrating API, Webhooks and Custom code beyond low code/no code tools. I have experience working with both SMB’s and large enterprises.
Some of my relevant work-
• For an Enterprise company with 500+ employees, I built end to end AI agents using Make for newsletter curation and Pinterest pin creation. It reduced the time for developing marketing assets from hours to minutes. The scenarios were made with robust error handling.
• For an education company, I integrated LMS with Airtable, Make, and CRM via API handling complex pagination and syncing data in real time.
• For a digital agency, I set up a smart call-routing system using Twilio and Airtable to automate lead handling.
I work more as an AI transformation partner for my clients rather than just a builder. Would love to learn about your day to day operations
Hello @Larry_Greene , 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
This looks like something I have worked on before with Notion, Make and Wix CMS setups.
Issues like incorrect content on dynamic pages usually come from how the data is being mapped into the CMS, how records are updated, or how the routing is structured in the scenario. I have helped debug and stabilize similar workflows so they run consistently without mismatches.
Happy to take a look at your setup and help identify what is causing the issue.
Hey @Larry_Greene , I’ve debugged similar Notion → Make → CMS publishing flows and can quickly isolate whether the issue is in field mapping, record updates, slug/routing logic, or Wix dataset bindings. The fastest approach is to trace one item end-to-end through Make, compare the payload against the exact Wix CMS collection schema, and verify how the dynamic page dataset is resolving content at render time. In cases like this, the problem is usually a mismatch between CMS item IDs, slugs, reference fields, or conditional update logic rather than a single visible error. I can review the scenario, inspect the Wix collection/dynamic page setup, and correct the mapping and routing so published content resolves consistently. If you want, send over the Make scenario export, a sample Notion record, and access/screenshots of the Wix CMS structure and I can start with a focused diagnostic.
Feel free to book a meeting with me here to discuss this further.
I’ve seen these “silent” mapping issues between Wix and Notion many times. Usually, the content isn’t actually “missing,” it’s just that the Wix dataset is tripping over a slug mismatch or a cache issue from an old schema.
I can help you dive into this right now and get it fixed.
Here’s what I’ll look at:
Mapping Audit: I’ll check your Make.com scenario to ensure the Notion properties are landing in the exact right Wix CMS fields (slugs and IDs are usually the culprits here).
Dataset Sync: I’ll verify the Wix dynamic page settings to make sure they are actually pulling from the live collection and not a filtered or outdated view.
Routing Fix: I’ll make sure the URL structure in Notion matches what Wix expects so the “Incorrect content” issue goes away for good.
I’m a systems developer and automation specialist. I spend my day-to-day building and debugging “Content Factories” and complex data syncs. I’m happy to jump in for those 2–4 hours to diagnose the root cause and get your publishing back on track.
What is your goal?
What is the problem & what have you tried?
Error messages or input/output bundles