Description
Summary What we need built Four Make.com scenarios in total. HubSpot → SimPRO: Scenario 1: Service request form → SimPRO job Trigger: HubSpot form submission (service request form where the customer has agreed to our call out fee) Action: Create the customer, site and job in SimPRO with all form fields mapped correctly Scenario 2: Demo booked → SimPRO quote Trigger: Demo meeting booked in HubSpot (we'll confirm the exact trigger with you) Action: Create the customer, site and quote in SimPRO SimPRO → HubSpot: Scenario 3: Quote accepted → deal updated Trigger: Quote accepted / converted to job in SimPRO (webhook) Action: Move the matching HubSpot deal to Closed Won and update the deal amount Scenario 4: Job completed → contact updated Trigger: Job marked complete in SimPRO (webhook) Action: Update a property on the matching HubSpot contact/company (e.g. last service date), which fires our existing HubSpot service reminder workflows Important details SimPRO's API requires records to be created in sequence (customer first, then site, then job or quote), so scenarios 1 and 2 need to be chained correctly Duplicate handling: check if the customer or site already exists in SimPRO before creating a new one Record matching for the return direction: scenarios 3 and 4 need a reliable way to match SimPRO records back to the right HubSpot deal/contact (e.g. storing the HubSpot ID in SimPRO or vice versa). We want your recommendation on the cleanest approach. SimPRO supports webhooks, so the return direction should be event driven, not polling Basic error handling so failed runs don't silently drop leads or updates We will provide access to a Make.com account, HubSpot and a SimPRO environment for testing Deliverables All four scenarios built, tested end to end and live in our Make.com account Short handover document (1–2 pages or a Loom video) explaining how each scenario works and how to fix common errors, so our admin can maintain it 2 weeks of post delivery support for bug fixes