---
title: "Connecting HubSpot to Qualy"
description: "How the Qualy–HubSpot integration works—two-way contact sync, payment rollups and the Qualy Payment custom object, timeline events, task sync, pay links from HubSpot, and the plan tiers that affect what's available."
lastModified: "2026-08-27"
lang: "en"
wordCount: 999
url: https://qualyhq.com/training/integrations/hubspot
---
## Site navigation

- [For schools](/international-education/for-schools.md) — For international education schools
- [For agents](/international-education/for-education-agents.md) — For international education agents
- [Explore](/training.md) — Watch videos on how to use Qualy
- [About](/about.md) — Learn about Qualy's mission and values
- [Pricing](/pricing)
- [5-min demo](/demo.md)
- [Login](https://dashboard.qualyhq.com)

# Connecting HubSpot to Qualy

> Keep your customers—and their payment status—in step between Qualy and HubSpot.

## At a glance

- **Intended for:** Admins & marketing
- **Category:** CRM
- **Reading time:** 5 minutes
- **Last updated:** 12th July 2026

## Quick summary

Connect HubSpot in Settings → Add-ons & integrations. Your Qualy customers sync to HubSpot contacts, and each contact carries payment information—how much is due, what's overdue and the next payment—as HubSpot properties, plus (on Enterprise) a "Qualy Payment" custom object and payment timeline events. Qualy → HubSpot runs automatically; HubSpot → Qualy is opt-in, so nothing flows back until you switch it on and set the condition (for example, only contacts at the "customer" lifecycle stage). HubSpot can even create a Qualy payment and get a pay link back. Contacts match by email; what's available depends on your HubSpot plan.

## Overview

The HubSpot integration keeps your customers—and their payment status—in step between Qualy and HubSpot, so your sales and success teams can see where every student stands without leaving the CRM. Once connected, Qualy will:

- **Sync customers to HubSpot contacts**
- **Write payment information onto each contact** (amount due, payments overdue, next due date, next payment and a pay link)
- On **Enterprise**, create a **"Qualy Payment" custom object** record per payment and log payments as **timeline events**
- Optionally **sync tasks** between the two systems

Qualy provisions what it needs on connect—a **"Qualy" property group**, the payment properties and (where your plan supports it) the payment custom object—so there's nothing to set up in HubSpot first.

## Which way it syncs

This is the key thing to understand:

- **Qualy → HubSpot is always on.** Customers, their payment information and (optionally) tasks flow to HubSpot automatically.
- **HubSpot → Qualy is opt-in.** Contacts only flow back once you enable it and set a **condition**; tasks only flow back when you turn task sync on.

The opt-in default is deliberate—it stops your whole HubSpot database from flowing into Qualy the moment you connect. Turn it on when you're ready, and scope it.

### Bringing HubSpot contacts into Qualy

When you enable contact sync-back, you choose **which** contacts qualify:

- **Everyone**, or
- Only contacts at a chosen **lifecycle stage** (the default is **customer**), or
- Only contacts with a specific **property value**.

Contacts already linked to a Qualy customer aren't pushed back and forth, so there's no sync loop.

## Payment information on a contact

Every synced contact carries its Qualy payment picture in the **Qualy** property group—how much is **due**, how many payments are **overdue**, the **next due date**, the **next payment amount** and a **pay link**. These are ordinary HubSpot properties, so you can build **lists, workflows and reminders** around them (for example, email everyone with an overdue payment).

On **Enterprise**, each payment also becomes a **"Qualy Payment" custom object** linked to the contact, and payments show up as **timeline events**—a full history right on the record.

## Creating payments from HubSpot

HubSpot can work the other way too: from a **CRM card** or a **workflow**, it can ask Qualy to create a payment and hand back a **pay link** to send the customer—so you can trigger a payment straight from a sales or success sequence.

## Plans and what's available

Some features depend on your HubSpot plan. **Custom objects** need **Enterprise**; **workflows** need **Professional** or above; **timeline events** need an app context. Where a capability isn't available, Qualy automatically **falls back to writing payment information onto contact properties**, which works on every plan—so the core sync always functions.

## Matching and rate limits

Contacts match by **email address**, backed by a link Qualy keeps between the two records. Qualy also paces its calls to stay within HubSpot's rate limits, so large syncs run smoothly in the background.

Keep emails consistent between Qualy and HubSpot—it's what lets contacts line up cleanly and avoids duplicates.

## Frequently asked questions

### Does HubSpot sync both ways?

Qualy → HubSpot is always on: customers, their payment information and (optionally) tasks flow to HubSpot automatically. HubSpot → Qualy is opt-in—contacts only flow back once you enable it and set a condition, and tasks only when you turn task sync on. This keeps HubSpot from pushing every contact into Qualy by accident.

### How do I control which HubSpot contacts come into Qualy?

With a condition. You can bring back everyone, only contacts at a chosen lifecycle stage (the default is "customer"), or only contacts with a specific property value. Nothing flows back until you switch it on.

### Where does payment information show up on a contact?

As HubSpot contact properties in a "Qualy" property group—how much is due, how many payments are overdue, the next due date, the next payment amount and a pay link. On Enterprise, each payment also becomes a "Qualy Payment" custom object record linked to the contact, and payments appear as timeline events.

### Why don't I see the custom object or timeline events?

They depend on your HubSpot plan. Custom objects need Enterprise; workflows need Professional or above. Without them, Qualy falls back to writing the payment information onto contact properties, which works on every plan.

### Can HubSpot create a payment in Qualy?

Yes. From a CRM card or a workflow, HubSpot can ask Qualy to create a payment and get back a pay link to send the customer—useful for triggering a payment straight from your sales or success workflow.

### How are contacts matched?

By email address, backed by a link Qualy keeps between the two records. A contact already linked to a Qualy customer won't be pushed back and forth, so there's no sync loop.

### Do I have to set anything up in HubSpot first?

No. On connect, Qualy provisions what it needs—a "Qualy" property group, the payment properties and (where supported) the payment custom object—so it's ready to use.

## Prefer doing this via the Qualy API?

Head over to our developer docs for everything you need—endpoints, examples, and simple how-tos.

[View API Docs](https://docs.qualyhq.com/docs)

## More on Qualy

**Industries**

- [For schools](/international-education/for-schools.md) — For international education schools
- [For agents](/international-education/for-education-agents.md) — For international education agents

**Support**

- [Training](/training.md)
- [System status](https://qualyhq.statuspage.io/) — Qualy system status
- [Product updates](https://changelog.qualyhq.com) — As we work on Qualy, here we spotlight what we’ve learned and updated across our products
- [Contact](/contact-us.md)

**Product**

- [Demo](/demo.md)
- [Enterprise](/enterprise.md)
- [Testimonials](/testimonials.md) — Learn what some customers have to say about Qualy
- [About](/about.md) — Learn about Qualy's mission and values
- [Blog](/blog) — International education payments blog by Qualy
- [Trust center](/trust.md)
- [API](/api.md) — Qualy API for international education payments
- [Zapier](/zapier.md) — Connect Qualy to 7,000+ apps with Zapier
- [NexPay](/nexpay.md) — Qualy + NexPay — automate everything around the payment

**Legal**

- [General terms](/terms-and-conditions.md)
- [Payer terms](/terms-for-payers.md)
- [Privacy policy](/privacy-policy.md)
- [BECS DDR](/becs-dd-service-agreement.md)