Pairing for HubSpot
Install, permissions, data and uninstall
What happens when you connect HubSpot to Pairing, what the app asks for and why, what it writes into your portal, and what stays behind if you remove it.
What the app does
Pairing by Denamico keeps HubSpot in sync with one other system, such as Salesforce, NetSuite or a system with a JSON REST API. It reads and writes the HubSpot records in your mappings, checks your HubSpot properties and dropdown values for changes, and holds any record that cannot sync with a plain-language reason so a person can fix it and replay it.
Pairing is set up with Denamico. Each client gets its own workspace in the Pairing portal, and the HubSpot app is how that workspace reaches your HubSpot portal.
Install
You need to be an admin of your Pairing workspace, and a user who can install apps in the HubSpot portal. Denamico may start the connection for you and send the HubSpot link; the steps are the same.
- In Pairing, open Connections and choose Connect a HubSpot portal.
- HubSpot asks you to sign in and choose the portal. Pick the portal you want.
- HubSpot shows the permissions screen. Review it (see the next section) and approve the app.
- You return to a Pairing page that names the HubSpot portal you chose and your Pairing workspace. Check both.
- Choose Connect. Nothing is connected until you do. Choose Cancel if it is not the portal or workspace you meant.
A HubSpot portal belongs to one Pairing workspace. A workspace can connect more than one HubSpot portal.
The permissions screen
HubSpot lists the permissions the app asks for. The required ones are always asked. The optional ones are asked on the same screen, and what you decline switches off the features that need them.
Required permissions
| Permission | What Pairing uses it for |
|---|---|
| oauth | Signing in to HubSpot as the app, and keeping that sign-in working. |
| crm.objects.contacts.read, crm.objects.contacts.write | Reading contacts that sync out of HubSpot, and creating or updating contacts that sync in. |
| crm.objects.companies.read, crm.objects.companies.write | The same, for companies. |
| crm.schemas.contacts.read, crm.schemas.companies.read, crm.schemas.deals.read | Reading your property definitions and dropdown values, to build mappings and to check every day for fields and values that changed. |
Optional permissions
| Permission | What Pairing uses it for |
|---|---|
| crm.schemas.contacts.write, crm.schemas.companies.write, crm.schemas.deals.write | Creating the Pairing properties and property group (next section), adding a dropdown option when a person applies that fix, and creating properties Denamico sets up for your integration. |
| crm.objects.deals.read, crm.objects.deals.write | Syncing deals. |
| crm.objects.line_items.read, crm.objects.line_items.write | Syncing line items on deals. |
| crm.objects.owners.read | Showing the list of HubSpot users when you choose who a HubSpot alert task is assigned to. |
| crm.import | Sending a large first load or bulk change to HubSpot as one import instead of many small writes. |
| crm.objects.projects.read, crm.objects.projects.write, crm.schemas.projects.read, crm.schemas.projects.write | Syncing HubSpot Projects, for portals whose HubSpot plan includes them. |
| crm.objects.custom.read, crm.objects.custom.write, crm.schemas.custom.read, crm.schemas.custom.write | Syncing custom objects, for portals whose HubSpot plan includes them. |
| crm.objects.<object>.read and .write, crm.schemas.<object>.read and .write, for tickets, quotes, orders, carts, invoices, appointments, courses, listings, services, leads, users, marketing events, subscriptions and commerce payments, plus e-commerce for products | Syncing another standard HubSpot object, only when a client asks for it and a mapping uses it. Some of these have read-only or no write permission in HubSpot. |
If a permission was not granted, the feature that needs it does not work for that portal. A request that HubSpot refuses for a missing permission fails with a message that names the permission. Choose Reconnect on the connection and approve the app again to grant it; HubSpot only offers a permission that was added to the app after your install on a fresh install, so Denamico may ask you to install again.
What Pairing creates in your portal
Pairing creates properties only when a feature needs them, and it never renames or deletes anything in your portal.
| What | When it is created | What it holds |
|---|---|---|
| Property group "Pairing", with the properties pairing_sync_status, pairing_last_error and pairing_last_synced_at, on each synced object | The first time a live sync with error writeback turned on touches that object. Error writeback is off unless an admin turns it on for an integration. | Whether each record last synced, was held or errored; the reason it is held and the field, never a field value; and when it last synced. |
| Property pairing_record_ref ("Pairing record ref"), in the same group | When Pairing sends a large load to HubSpot as an import. | A unique reference that links an imported record back to its source record. |
| Property pairing_demo_id ("Pairing demo") | Only in the demo portals Denamico runs for sales demos. Pairing does not create it in a client portal. | The id of the demo that created the record, so a demo can be reset. |
| HubSpot tasks | When an admin sets an alert rule to create a HubSpot task, and an alert fires. | The alert text (workspace, integration, event and counts, no record values), linked to the records involved. |
| Dropdown options | When a person applies the "add this option" fix to a held record. | The new option on an existing dropdown property. |
| Properties and pipelines Denamico sets up | When Denamico staff create them for your integration, through your connection. Each action is recorded in the audit log. | Whatever your integration needs. Existing properties are never changed. |
During a rename from the product's earlier name, each Pairing property is also written under its earlier plumb_ name, in a second property group that is also labelled Pairing. You may see both sets. Pairing does not delete either.
What you see in HubSpot
The app adds two cards for your record pages, and two pages: Synced records and Sync health. A HubSpot admin places the cards once per object with Customize on a record page; HubSpot does not let an app place or reorder cards itself.
- Pairing sync, in the middle column: the record's sync status and when it last synced, the properties Pairing writes into HubSpot and the ones it reads from HubSpot, as HubSpot's own property lists, and a table of the records Pairing associates with it.
- Pairing status, in the sidebar: the sync status, any held sync with its reason and a link to fix it in Pairing, and the records Pairing associated this one with.
- Synced records, a page in the app: a tab per synced object, with a column for each synced property and each kind of record Pairing associates, a held-only filter, and search. It reads records with the viewer's own HubSpot permissions.
- Sync health, a page in the app: for the last day, week or month, the share of records synced rather than held, held records by cause, each integration's last run and failures in a row, and the connections' and alerts' state. Counts only.
The cards ask Pairing for names only: which properties and associations sync, the last outcome, and why a sync is held. The cards and pages never show a held value, and they change nothing; fixes happen in Pairing. Property values on the cards are shown by HubSpot under the viewer's own HubSpot permissions. Anyone who can open the record can see the cards. The cards appear on contacts, companies, deals, tickets, orders, carts, invoices, products, quotes, subscriptions and custom objects.
Disconnect and uninstall
A Disconnect action in Pairing is coming. Today an admin cannot disconnect a HubSpot portal from inside Pairing. To stop Pairing working in your portal, uninstall the app in HubSpot, or ask Denamico through support to pause your syncs.
To uninstall
- In HubSpot, open Settings, then Integrations, then Connected apps.
- Choose Pairing by Denamico, then Actions, then Uninstall.
What happens when you uninstall
- HubSpot revokes the app's access and stops sending change notifications. Pairing is not told when this happens.
- The next time Pairing calls HubSpot, HubSpot refuses it. The connection then shows Sign-in failed in Pairing, and syncs that use it stop. Records that needed HubSpot are held with the reason "Sign-in to a system failed", so none are lost, and an alert rule for an expired sign-in can email you.
- Pairing keeps your workspace as it was: the connection, mappings, sync history and held records. It deletes nothing on uninstall.
- To start again, choose Reconnect on the connection and approve the app in the same portal. Then replay the held records.
What stays in HubSpot
- Every record Pairing created or updated stays, with its values.
- The Pairing properties and property groups stay, with whatever they hold. Pairing does not remove them. You can delete them in HubSpot under Settings, then Properties, once you no longer need them.
- HubSpot tasks Pairing created stay until you delete them.
Having your data removed from Pairing
Ask Denamico through support and we will remove your workspace's data from Pairing. This is done by hand today, because some stored data has no automatic purge yet.