Settings
HubSpot Connection Health New
Everything PDF CreateMate does happens inside your HubSpot portal: it reads the record, uploads the file, and writes the file onto a property. Each of those asks for a permission, and your portal decided which of them to grant when the app was connected.
The HubSpot Connection Health card in Settings shows which of those permissions your portal actually granted, so you can see the gap instead of guessing.
The card reports what your portal granted. It does not predict what each missing permission breaks: HubSpot often allows more than the granted permissions suggest, so a permission listed as not granted is a gap worth closing rather than proof that something has already failed. The one exception is create properties, which is described below.
What the card shows
At the top, the connection itself:
- Portal ID — the HubSpot portal PDF CreateMate is connected to. Worth checking first if documents are landing somewhere you did not expect.
- Connected by — the person whose HubSpot login authorised the app. The permissions are theirs, not the organization's.
- Connected on — when that authorisation happened.
- Connection — Active or Not active.
Below that, one row per capability you depend on:
| Row | What it covers |
|---|---|
| Uploading documents | Putting the generated file into HubSpot's file manager |
| Workflow action | The PDF CreateMate action inside HubSpot workflows |
| One row per record type | Contacts, Companies, Deals, Tickets, Orders, Projects — only the ones your portal has |
| Deal line items | Line-item tables in Deal templates. Only shown if you use Deals |
| Custom objects | Your portal's own object types. Only shown if your portal has any |
Each row carries a status:
| Status | Meaning |
|---|---|
| Granted | Every permission this capability asks for was granted |
| Partly granted | Some were granted and some were not |
| Not granted | None of them were granted |
Reading a row that needs attention
A row that is not Granted expands into two things: what your portal did not grant, and what to look for in HubSpot.
For a record type, for example:
- read records — your portal didn't grant PDF CreateMate permission to read these records.
- update records — your portal didn't grant PDF CreateMate permission to update these records.
- create properties — publishing a template fails: HubSpot refuses to create the property the document is stored in.
create properties is the one row that states a consequence, because it is the one we can reproduce: without it HubSpot refuses the request outright, and a template cannot be published. The other rows state the permission and stop there. If a row is missing create properties alongside another permission, that is the sentence you see — the quoted lines underneath still list every permission you have to tick.
In HubSpot quotes HubSpot's own wording for each missing permission, word for word — for example "Create, delete, or make changes to contacts." This matters because HubSpot's approval screen lists permissions by that description, not by a technical name. Copy the line from the card, find the same line on the approval screen, and tick it.
Record types your portal cannot use
Some record types are only available if your portal granted an optional permission for them. Without it, the record type never appears in PDF CreateMate at all, so there is nothing to click and nothing to fix from inside the app.
The card names those record types in a separate note. For why the permission may be greyed out on HubSpot's approval screen, and what to do about it, see Object Missing or Permission Locked.
Check again
Opening Settings does not call HubSpot. The answer was recorded when your portal last authorised the app, which is the only moment it can change.
Check again re-reads the permissions from HubSpot on demand. Use it right after a reconnect, or when you want to confirm the card is not showing you a stale answer.
If PDF CreateMate cannot reach HubSpot, the card says so instead of listing permissions. That message means the check did not happen — it does not mean a permission is missing. Try again in a few minutes.
Who can see it, who can fix it
Every member of your organization can see the card. The person who notices that documents stopped arriving is usually not the organization owner, and they should not have to open a support ticket to find out why.
Reconnecting is a different matter, and only an organization owner can do it. If you are not the owner, the card tells you to ask them.
Fixing a missing permission
- In Settings, note the permissions the card lists under In HubSpot.
- Click Reinstall HubSpot App, signed in to HubSpot as a Super Admin.
- On HubSpot's approval screen, approve every permission — including the optional ones. The lines you noted in step 1 are the ones that were not ticked last time.
- Complete the connection. The card updates as soon as you return.
- If anything still looks wrong, click Check again.
The rest of the HubSpot section
Two more actions live on the same Settings page:
- Reinstall HubSpot App — re-runs the HubSpot authorisation for the portal you are already connected to. This is how you grant a permission you declined, and it is the fix for almost everything the health card reports.
- Disconnect — removes the connection entirely. Templates stay, but nothing can be generated until you connect again. You are asked to type DISCONNECT to confirm.
Reinstalling is almost always what you want. Disconnect is for moving to a different portal or stopping altogether.
Related
- The Document Generates But Is Not On The Record
- Object Missing or Permission Locked
- HubSpot Connection — connecting, changing and disconnecting a portal
- Workflow Actions