Have sent you a DM as well. Would love to help you integrate Hubspot with ClickUp. I run an automation studio called Automation Jinn where we help companies automate their processes and increase efficiency. I am Make advanced certified, ClickUp Expert certified and Hubspot Sales/Marketing Hub certified with a background in computer science so quite comfortable in integrating API and custom code. I have experience working with both SMB’s and large enterprises.
Some of my relevant work-
• For a fintech startup in Amsterdam (raised €8.1M), automated there lead flows in the CRM and built a custom Slack bot to flag churn risks.
• Built a workflow that enriches and qualifies inbound leads using Bright Data MCP while updating the CRM in Hubspot for both qualified and unqualified.
• For an education company, I integrated LMS with Airtable, Make, and their CRM via API handling complex pagination and syncing data in real time.
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 @3DWalkabout , I can build and stabilise this HubSpot ↔ ClickUp workflow in Make with clean logic, deduplication, and reliable write-backs to HubSpot. I’ve handled similar automations where HubSpot deal stage changes trigger task creation, custom field mapping, task status sync, and ID/status updates back into HubSpot without duplicate records. I’d also review any existing scenarios to simplify routing, tighten filters, and fix edge cases that usually cause bad deal selection or repeated runs. If needed, I can extend the setup into Google Sheets and Forms while keeping everything maintainable and easy to troubleshoot. Send over your current scenario(s), the HubSpot deal rules, and the ClickUp task structure, and I can map the fix quickly. You can book a meeting with me here to discuss this further.
Hello @3DWalkabout , 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 is a solid use case — I’ve worked on similar HubSpot ↔ ClickUp automations in Make, especially around deal-to-task workflows and syncing data back into CRM.
From your requirements, the key areas would be:
• mapping HubSpot deal stages → ClickUp task creation
• syncing task IDs/status back to HubSpot
• preventing duplicates with proper filters + data structure
• stabilizing scenarios with error handling and clean logic
I also have experience improving messy scenarios and simplifying them for reliability.
A couple of quick questions about your Project:
Are you triggering task creation on specific deal stages or multiple stages?
Do you already have an existing scenario that needs fixing, or is this from scratch?
How are you currently handling duplicate prevention (if at all)?
Happy to review your setup and suggest improvements.
Looking forward to hearing from you soon Tim!
Website Portfolio / Work Samples: Click here to check my previous automation setup.
Book a Call: Click here to book a walkthrough call session.
Email: folafoluwaolaneye@gmail.com
The kind of automation work you are asking for is where I tend to be strongest, because it sits right in the middle of systems logic, operational reliability, and messy real-world business rules. I am a strong fit when a workflow has to do more than fire once and look good in a demo. It has to select the right record, create the right downstream action, write clean data back into the source system, and keep doing that without duplicates, bad filters, or brittle logic every time someone changes a stage or edits a field.
I would start by auditing the current data model on both sides before touching the scenarios. In work like this, bad automation usually comes from weak field structure, unclear ownership, or too many assumptions about what a stage or property means.
I would identify the exact HubSpot deal conditions that should trigger task creation versus task updates, because those need to be separated cleanly or the scenario gets noisy fast.
I would define a dependable cross-system key early so one HubSpot record maps to one ClickUp task and stays tied together across future updates. That is the first step in stopping duplicates.
I would review every filter, router, and conditional branch in Make to confirm records are being selected for the right reason. Most broken automations fail here, not in the modules themselves.
I would decide which fields are owned by HubSpot and which are owned by ClickUp before any write-back logic is finalized. Without that, you end up with status conflicts and accidental overwrites.
I would split creation logic from sync logic so the workflow stays maintainable. Trying to force everything into one oversized scenario usually creates the exact instability you are trying to get rid of.
I would normalize field values before they move between systems, especially if stage, owner, priority, service type, or custom properties affect task behavior.
I would build in guardrails for reruns, partial failures, and retries so an API hiccup or timeout does not create duplicate tasks or incomplete write-backs.
I would test against real operating cases, not just happy-path samples. That includes edited deals, reverted stages, missing properties, repeated webhook events, and task updates coming back from ClickUp.
I would leave the setup modular and readable so future Google Sheets or Google Forms work can be added without turning the whole system into a pile of fragile one-off logic.
A few relevant examples from my work:
I built a full automation and systems integration layer from the ground up using Zapier and Make for a heavy equipment and service business with multiple operational paths including sales inquiries, parts and service requests, internal notifications, CRM synchronization, follow-up workflows, and routing logic. The hard part was not connecting apps. It was designing how records should be filtered, categorized, tagged, routed, and handed off without creating duplicates or bad downstream data. That ties directly to your project because HubSpot to ClickUp work fails for the same reason when trigger conditions, field mapping, and write-back rules are not structured properly.
I built a complex automation framework using Zapier and Make to handle lead capture, segmentation, internal routing, CRM synchronization, marketing-to-sales handoff, and structured cross-system data movement. That work required building reusable workflow patterns, conditional routing, duplicate prevention, clean mappings, and data governance across multiple systems. It is highly relevant here because your setup needs the same kind of discipline around filters, ownership, and reliable state movement between platforms.
**
I built a full operational automation system from the ground up using Zapier and Make for quote requests, service inquiries, customer follow-up, CRM updates, internal alerts, and lifecycle automation beyond the first submission.** I had to account for incomplete data, branching logic, status changes, stale records, and maintainability so the workflows stayed useful over time. That ties directly into your project because reliable HubSpot and ClickUp automation is not just about creating a task once. It is about making sure the record continues to behave correctly as the deal moves.
If you want to talk through the current setup, I would be glad to jump on a call and review how the existing scenarios are structured.
Are you working from an existing scenario that needs cleanup, or would it be smarter to rebuild the core logic cleanly?
Which HubSpot deal stages should create a task, and which should only update one?
What is the current duplicate prevention method, and where is it breaking down?
Which specific fields need to write back into HubSpot, and which should stay controlled by ClickUp?
Do Google Sheets and Google Forms need to be part of the first phase, or should the HubSpot and ClickUp flow be stabilized first?
I’ve built dozens of HubSpot and ClickUp integrations, so I know exactly where they usually break—mostly on duplicate tasks and messy filters. I can help you build a system that just works.
What I’ll do:
Clean Logic: I use “Search and Update” (Upsert) so you never get double tasks in ClickUp.
Two-Way Sync: I’ll make sure HubSpot knows exactly what’s happening in ClickUp (Task IDs, statuses) in real-time.
Cleanup: I specialize in fixing “spaghetti” scenarios. I’ll simplify your flows so they’re easy to manage and don’t crash.
Reliability: I add error handling to every scenario so they don’t stop if one deal has missing data.
My Experience:
I’m a developer at heart, so I understand the APIs behind these tools. You can see my engineering style here: https://mikedevai.netlify.app/
This is exactly the kind of work I specialize in. I’ve built and optimized Make.com automations connecting HubSpot with task systems like ClickUp—handling deal-based task creation, writing data back (IDs/status), and fixing issues like duplicates and incorrect filtering.
I’ve also cleaned up messy scenarios by restructuring routes, adding proper filters, and ensuring reliable execution.
Check my profile: 
Book a quick call:Calendly - Automaxion