Intugrace | Elopage and HubSpot · General

What was built

Intugrace runs payments on Elopage and had a CRM that knew nothing about them, with support in a third system. The work made HubSpot the single place where a customer, their payments and their support history meet, with Make.com carrying every Elopage event into it.

Area	Description
Elopage sync	Every Elopage product and subscription plan synced into HubSpot, with the payment events that follow processed in Make.com
Payment edge cases	Chargebacks, refunds, failed payments and retries handled explicitly and stored as custom objects against the deal
HubSpot CRM	Deals, contacts and deal-stage logic aligned to the payment model, including the fix that marks a completed subscription Closed Won instead of Closed Cancelled
Landing pages	The Elopage product layout rebuilt as a HubSpot landing page across desktop, tablet and mobile
Support consolidation	ZenDesk retired, ticketing moved into HubSpot alongside contact and payment history
Nonpayer handling	Three HubSpot workflows covering ticket creation on failed payment, the Mahnung sequence, escalation to the lawyer list and automatic closing on payment
Data migration	Orders, transfers, contacts and companies migrated out of Elopage and ActiveCampaign, plus a custom object linking deals to their transfers
Helper service	A HubSpot helper maintained through three major versions, plus scenario break handling at scale

Nonpayer handling

The nonpayer system is the core workflow. When a payment fails or a contact goes overdue, HubSpot opens a support ticket, queues the dunning emails (Mahnung-Emails) in sequence, and escalates to a lawyer list if it stays unresolved:

• Nichtzahler: Ein Ticket öffnen — ticket creation on failed payment
• Nichtzahler: Mahnung-Emails — timed reminder emails
• Nichtzahler: Schließen von Tickets bei Zahlung — closes the ticket when payment clears

Make.com scenarios

All core logic runs through Make.com: the Elopage scenarios, a webhook for failed payments, and the full scenario set deployed to production after a staged review. Transfer dates, invoice creation dates and payment success dates all land in HubSpot as date fields.

Tech stack

Technology	Role
Elopage	Payments and the course platform, kept
HubSpot	CRM, deals, tickets, dunning workflows, landing pages
Make.com	Every sync between Elopage and HubSpot
ActiveCampaign	The contact source migrated into HubSpot

Project stats: 436 tasks, ~1114h over 23 months.