Every contact in the portal
QuickGrow calls the HubSpot contacts API with your token, takes 100 records a page and follows HubSpot’s cursor until there is no next page left. It reads the full list on every run, not only the ones that changed.
HubSpot
HubSpot keeps the record. QuickGrow does the talking.
One private app token connects your portal. Every six hours QuickGrow reads your HubSpot contacts and deals through HubSpot’s own API and reports what each run found. Nothing is written back to HubSpot, and nothing is copied into your QuickGrow contact list — the messaging runs on the list you build here, across email, SMS and WhatsApp.
Read-only — nothing written to HubSpotOne token, one fieldRead again every 6 hoursToken encrypted when saved
01What connecting does
It reads, it counts, it tells you.
Worth being clear on before you set it up, because it decides what the rest of this page is worth to you. The HubSpot connection is an authenticated read on a schedule: it proves the token works, it walks your contacts and your deals, and it reports the numbers. It does not move records in either direction.
Every deal, in the same pass
Deals are read the same way, at the same time, 100 to a page. QuickGrow keeps no deal record of its own, so what a deal read gives you is the number — confirmation the token still reaches your pipeline, and how big that pipeline is.
A count and a status, not a copy
A run finishes with how many contacts and how many deals it read, the time it finished, and the connection marked completed or failed. That is the whole output. No record is created in QuickGrow and none is changed in HubSpot.
02Connect
One token. That is the entire setup.
If you can reach your own HubSpot settings you can finish this in a few minutes, without a developer and without handing anyone your login.
Make a private app in HubSpot
In your own HubSpot account, under Settings, create a private app and give it read access to contacts and deals. HubSpot shows you an access token once. There is no marketplace listing to install and no approval to wait for.
Paste the token into QuickGrow
Settings, then Integrations, then HubSpot. One field: that token. It is encrypted the moment it is saved and is never sent back to the browser, not even to you. Your HubSpot password is never involved.
The first read runs on the schedule
Every switched-on connection is read again every six hours, so the first pass happens on the next run rather than the second you press Connect. Teams that want a read on demand can call the sync endpoint on the API.
You get told what happened
The owners and admins on your account are notified when a connection is made, when one is removed, and when a run fails, with the reason it failed. Nobody connects or disconnects a portal quietly.
03How a read works
Exactly what each run asks HubSpot for.
Two kinds of record, both read the same way. Nothing in this table is inferred — it is what the connector does.
| Contacts | Deals | |
|---|---|---|
| What it reads | Your HubSpot contact records | Your HubSpot deal records |
| Per page | 100, then the next cursor | 100, then the next cursor |
| First run | The whole list | The whole list |
| Every run after that | The whole list again | The whole list again |
| What the run records | How many were read | How many were read |
| Created, edited or deleted in HubSpot | No | No |
| Added to your QuickGrow contact list | No | No |
04What you build on
The messaging runs on your QuickGrow list.
This is the part that earns its keep. Your QuickGrow contact list — built by upload, by form or popup, or pushed in from your own code — is what groups and journeys work on, and it reaches people on email, SMS and WhatsApp from one account and one bill.
Journeys
Build the follow-up once and leave it running.
A journey is a trigger and then steps: send on any channel, wait a real amount of time, branch on a condition, add or remove a tag, update a field, or call a webhook of your own. One journey can use all three channels, so a nudge opens on email and finishes on WhatsApp.
- A date held on the contact is the trigger that runs on its own: pick the field, set how many days before or after, and QuickGrow checks every minute — renewals, review dates, appointments, birthdays
- Importing a list starts the journeys that begin with a new contact, so a welcome sequence can run straight off the upload
- The other triggers are a contact updated, a tag added or removed, a form submitted, and a campaign opened or clicked
Groups
Count the audience before you spend on it.
A group is a few rules, and it shows you how many contacts match while you are still writing them. Add a rule, watch the number move, then send to exactly those people.
- Rules on tags, where the contact came from, their status, an engagement score, when they last engaged, and when they were added
- Join the rules with and / or, and the count stays live as new contacts arrive
- What a rule cannot see is deal value, stage, or anything else that lives in HubSpot — to target on it, carry it over as a tag when you import
05The detail
What is kept, what is safe, and what happens when a run fails.
On every run
- Contacts and deals are read together, each paged through to the end of the list
- The connection shows what it is doing: syncing, completed, or failed
- The time of the last successful read is kept, and only moves when a run finishes
The token
- One field, one token: a read-only private app token made in your own HubSpot account
- Encrypted when it is saved, and never returned to the browser afterwards
- The connector only ever calls HubSpot itself, so there is no address to mistype and nowhere else a call can be sent
When something breaks
- The connection is marked failed and keeps the last good read time
- Your account owners and admins are notified, with the reason the run failed
- A wrong or expired token shows up as a failed run rather than a quiet one
Automatic every 6 hours Admins told when a run fails Token encrypted at rest Never shown back to the browser
06Cost
What connecting HubSpot costs you.
Nothing on its own. What you pay depends on how much you send, and on whether you bring your own mail server or SMS account.
The connector is not a separate line
You pay a platform fee that covers the tooling — contacts, groups, journeys, the shared inbox and the reports — and then you pay for the messages you send. Connecting HubSpot adds to neither.
Buying volume cuts the fee
Managed volume waives part of the platform fee, and buying across email, SMS and WhatsApp at a high enough tier waives it entirely. A longer billing term discounts the fee and the volume on separate ladders.
Bring your own mail or SMS
Point QuickGrow at your own mail server or SMS account and the platform fee is all you pay. WhatsApp runs on your own number too — you pay Meta directly, at Meta's own rate, with zero QuickGrow markup and nothing committed monthly.
07Questions
Before you connect.
Does a HubSpot contact become a QuickGrow contact automatically?
Not today. The connector reads your portal and reports how many contacts and deals it saw; it does not create anything in QuickGrow. Your contact list here is built in three ways: upload a spreadsheet, capture people with a form or a popup on your own site, or push them in from your own code through the API. If automatic contact creation is the piece you are waiting on, say so on the contact page and we will tell you where it stands.
So how do I get my HubSpot list in today?
Export the list you want from HubSpot as a CSV and upload it under Contacts. QuickGrow reads the header row, proposes a column mapping and shows you a preview before anything is saved. You choose the tags every row carries in and the consent it records for the channel. People already in your list are matched on their email address and updated rather than duplicated, and each genuinely new contact can start a welcome journey on the way in.
Can QuickGrow change anything in my HubSpot portal?
No. The connection reads. Read access to contacts and deals is all the token needs, and no contact, deal, property or note is created, edited or deleted in HubSpot. Everything moves one way.
How often does it read, and can I force a read?
Every six hours, automatically, for every connection that is switched on. The Integrations screen shows the connection and lets you remove it; there is no sync button on it. If your team needs a read on demand, the API has an endpoint for it, and the answer comes back as the same counts.
Can a new deal, or a deal changing stage, fire a message?
No. Journeys in QuickGrow start from its own events: a contact created or updated, a tag added or removed, a form submitted, a campaign opened or clicked, or a date held on the contact. A deal moving in HubSpot is not one of them — the six-hourly read counts deals, it does not raise an event. For follow-ups that must be automatic, the date-based trigger is the one to build on: a renewal date, a contract end, a review date. Anything else you run as a campaign to a group.
Do I need a HubSpot marketplace app, or an OAuth screen?
Neither. You create a private app inside your own HubSpot account and paste its access token into QuickGrow. One field, no redirect, no password shared, and you can delete the app in HubSpot whenever you want.
I connect a store as well. Is this connector the same?
The shape is the same: credentials you make yourself, read-only, on the same six-hour schedule, encrypted at rest. Two differences are worth knowing. Shopify and WooCommerce read customers, orders and products and ask only for what changed since the last good run, while HubSpot reads contacts and deals and walks the full list every time. And the store connectors call an address you type, which is checked before every call, while HubSpot has no address to give — only the token.
What happens when I disconnect?
The scheduled reads stop and the connection is marked inactive. Nothing further is read from your portal, and your admins are told it happened. Deleting the private app in HubSpot closes it off from that side as well.
Keep the record in HubSpot. Do the talking here.
One token connects the portal. Email, SMS and WhatsApp sit in the same account, on the same bill, with the groups and journeys that decide who hears what.