HubSpot
The HubSpot integration keeps your HubSpot CRM up to date with what happens in Full Fabric. An administrator connects one HubSpot account for the institution; Full Fabric then creates and updates a HubSpot contact for each profile, a deal for each journey, records the emails it sends on the recipients' contact timelines, and attaches uploaded files to contacts and deals as notes. Sync runs one way, from Full Fabric to HubSpot: changes made in HubSpot are not copied back, and Full Fabric never deletes HubSpot records.
This page covers the connection, contacts, emails and files. Deals are configured with sync rules, described in HubSpot deals.
How It Works
Every sync runs in the background a few moments after the change, behind other background work. Failed syncs are listed in Sync management.
Connecting HubSpot
- Go to Settings → Other integrations → HubSpot (in the Other group). The link only appears when the HubSpot integration is enabled for your institution.
- Click Authenticate. HubSpot asks you to sign in and choose the account to connect.
- Approve the access Full Fabric requests: contacts and deals, plus optional access to files. File access is only needed to sync attachments.
- HubSpot returns you to the settings page, which now shows Active and the sync cards.
| Card | Contents |
|---|---|
| Profile → Contact | Sync profiles toggle, Sync files as Notes toggle, contact field mapping |
| Email → Engagement | Sync emails toggle |
| Journey → Deal | Sync journeys toggle, Sync application files as Notes toggle, sync rules (see HubSpot deals) |
| Advanced | Account ID (the HubSpot account), Authenticated profile ID (the Full Fabric user who connected it), Re-authenticate button |
All toggles start off, and each one saves as soon as you click it. Full Fabric renews its HubSpot access automatically; use Re-authenticate if HubSpot stops accepting it, or to grant file access later.
Disconnecting
Click De-activate and confirm De-activate HubSpot?. This:
- Removes the connection and turns every sync off
- Resets the contact field mapping to its required rows
- Deletes every sync rule except the default rule, which is reset to the default deal name with no stages
- Forgets which contacts, deals and emails were linked to Full Fabric records
Nothing is deleted in HubSpot. After connecting again, profiles are matched to their existing contacts by email address.
Profiles to Contacts
Turn on Sync profiles on the Profile → Contact card, then map fields in the table below it (Full Fabric field → HubSpot property).
- Email, first name and last name are always mapped and can't be changed.
- Add a mapping in the empty last row. A row saves automatically once both sides are filled; remove a row with its × button.
- Read-only HubSpot properties are not offered, and each property can only be mapped once.
- Mappable fields are native profile fields and profile fields of these types: single-line text, paragraph text, number, email, date, date and time, country, checkbox, dropdown, sequential ID, address (each part separately) and phone.
How values are sent:
- An empty field clears the HubSpot property.
- For checkbox and dropdown fields, each selected option is sent as its HubSpot value when the option set defines one (see Option sets); several options are joined with semicolons.
- First UTM source, medium, campaign, content and term are first-touch fields: once the contact holds a value for the mapped property, Full Fabric never overwrites it.
When contacts sync
| Event | Result |
|---|---|
| A profile is created | The contact is found or created, then updated with every mapped field |
| A profile is updated | Synced only when a mapped field changed |
| A policy is accepted | Synced when a field of that policy type (communication, privacy, cookies or data processing) is mapped |
| A journey creates its first deal | A contact is created with email, first and last name if none exists, even when Sync profiles is off |
Full Fabric finds the contact by the link it stored on an earlier sync, otherwise by the profile's email address (HubSpot's primary or additional email addresses). If no contact matches, it creates one with email, first and last name first, then sends the full mapping, so a failed update still leaves the contact in place for the next sync.
Emails to Engagements
Turn on Sync emails on the Email → Engagement card. Each email Full Fabric sends is then recorded once in HubSpot as an email on the contacts of its To recipients, with the send time, subject, HTML and text body, sender, and To and CC addresses.
- BCC recipients are never included.
- Only recipients who already have a HubSpot contact are linked; email sync never creates contacts. An email with no matching recipient is skipped without an error.
- Emails received into Full Fabric are not synced.
Files to Notes
| Toggle | Card | Also needs | What syncs |
|---|---|---|---|
| Sync files as Notes | Profile → Contact | Sync profiles | Files on the profile: general uploads and file fields on the profile, its journeys and its experience records |
| Sync application files as Notes | Journey → Deal | Sync journeys | Files uploaded in an application |
Both toggles need HubSpot file access. Without it they are disabled and the card shows HubSpot file access not granted; click Re-authenticate and grant file access.
- Profile files sync when a file is uploaded to the profile. Each run sends every profile file not yet sent, so earlier files are picked up too. Files only attach to an existing contact; if the profile has none yet, they wait for the next upload.
- Application files sync when the application is submitted and attach to the deal of each journey the application created. If a deal does not exist yet, Full Fabric checks again up to five times over about seven and a half minutes, then attaches the files to the deals that exist.
Each file is uploaded once, as a private file in a fullfabric folder of the HubSpot file manager, and appears on the record's timeline as a note such as "Full Fabric profile attachment: file name". Files that have not passed the virus scan, or are encrypted, are not sent.
Common Failures
Failed syncs appear in Sync management with App HubSpot and Trigger Type Event. A failure caused by a HubSpot rate limit or a temporary HubSpot outage is retried automatically up to five times, with growing pauses of about 10, 20, 40 and 80 seconds, and is only listed if the last attempt fails. Other errors are not retried. There is no re-run button: profiles and journeys sync again at their next qualifying change and profile files at the next upload, while a failed email is not sent again.
| What you see | Usual cause | Fix |
|---|---|---|
An error starting with Profile field "<field>" (HubSpot property "<property>"), or Journey field, followed by HubSpot 400 VALIDATION_ERROR |
HubSpot rejected the value of a mapped field, for example an option the property does not allow | Correct the mapping, add a HubSpot value to the option, or adjust the property in HubSpot |
HubSpot property "<property>" (no FullFabric field mapping) |
HubSpot rejected a property that is not in your mapping | Check that property's requirements in HubSpot |
| A HubSpot 401 or 403 error, or an error renewing access | The connection was revoked or has expired | Click Re-authenticate |
| A HubSpot 429 error | The rate limit was still hit after every retry | The record syncs again on its next change |
| Attachment toggles disabled | File access was not granted | Re-authenticate and grant file access |
Sync rule errors shown when saving a rule are covered in HubSpot deals.
Permissions
| Action | Who can do it |
|---|---|
| Connect, configure or de-activate HubSpot | Staff with Global integrations (core.institutions.global_integration_settings), see Integrations |
| See failed syncs | Staff with Sync management, see Sync management |