HubSpot Deals

With journey sync turned on, Full Fabric creates a HubSpot deal for each journey that reaches a lifecycle state you have mapped to a deal stage. The deal is linked to the person's HubSpot contact, and Full Fabric keeps its stage, name and mapped properties up to date as the journey moves through the lifecycle. Which stages and properties apply is set by sync rules, so different programmes and courses can use different pipelines.

Connecting HubSpot, contacts, emails and files are covered in HubSpot.

Turning It On

In Settings → Other integrations → HubSpot, turn on Sync journeys on the Journey → Deal card. The card then shows the Sync application files as Notes toggle (see Files to Notes) and the Sync rules list. Journeys only sync once a rule maps their lifecycle state to a deal stage.

Sync Rules

Each rule is a card with these parts:

Part Purpose
Rule name Required
Scope The Programmes and Courses the rule covers
Deal name Template for the HubSpot deal name
Deal stages Which deal stage each lifecycle state maps to
Field mappings Which journey, product and profile fields fill which deal properties
Sync toggle Turns the rule on or off; on a saved rule it takes effect immediately

Click Add sync rule to create a rule, then Save on its card. An institution can have up to 500 rules.

The default rule

The rule marked Default covers every programme and course that no other rule covers. It has no scope and can't be removed. While there is no default rule, the first rule you add becomes it.

Scoped rules

Every other rule needs at least one programme or course. A programme or course can belong to one rule only: those already used by another rule are not offered, and appear as "name (in another rule)" if a rule still holds them. All classes of a selected programme follow its rule.

Which rule applies

When the default rule is off, the list shows Other programmes and courses won't sync with a Turn on default rule button.

Deal name

The deal name is required and defaults to {{product.long_name}} - {{profile.first_name}} {{profile.last_name}}. Type text or use Add merge field to insert fields; the Example box previews the result, and a broken template shows Invalid deal name with the reason.

Deal stages

Map each Full Fabric lifecycle state to a HubSpot Deal stage. Stages from any HubSpot pipeline can be chosen and appear as Pipeline › Stage; the rule sets both the deal's pipeline and its stage. Each lifecycle state can be mapped once per rule. A journey in a state the rule does not map keeps its current deal stage.

Field mappings

Map Full Fabric field to HubSpot property. Fields are labelled by source: Class, Course, Programme, Product, Journey and Profile. Read-only deal properties are not offered, nor are the pipeline and deal stage, which the rule's stages control. Values follow the same rules as contact fields: empty fields clear the property, option set HubSpot values are used for checkboxes and dropdowns, and first UTM fields are never overwritten (see Profiles to Contacts).

Saving a rule

Save checks the rule against your HubSpot pipelines. An error appears at the bottom of the card:

Message Fix
Add a name for this rule. Fill in Rule name
Add at least one programme or course. Only the default rule can be left without a scope. Choose a programme or course
Stages map state more than once Keep one row per lifecycle state
stage id does not exist in HubSpot, or does not belong to pipeline id The stage was removed or moved in HubSpot; pick the stage again
programme or course id is scoped by another rule Remove it from one of the two rules
none of this rule's programmes or courses exist any more Add a programme or course, or remove the rule
a tenant can have at most 500 sync rules Remove or merge rules

When Deals Sync

Event Result
A journey is added, or changes lifecycle state, and its rule maps the new state The deal is found or created, moved to the mapped stage, and its name and mapped properties are updated
A journey moves to a state its rule does not map Nothing is sent
A mapped journey or profile field changes on a journey that already has a deal The deal's name and properties are updated; its stage is left as is
A journey is swapped for another product The existing deal moves to the new journey and is renamed and re-staged, instead of a second deal being opened

Before creating a deal, Full Fabric looks for a deal on the person's contact with the same name that none of their other journeys already holds, and reuses it. If the person has no contact yet, one is created with email, first and last name. A new deal is created with its name and stage first, then updated with the full mapping, so a failed update still leaves the deal in place.

Note: Turning on journey sync or changing a rule does not sync existing journeys straight away. Each journey syncs at its next qualifying change. Removing a journey in Full Fabric does not change or delete its deal.

Failed deal syncs appear in Sync management as User Journey or Create User Journey; see Common Failures.

Permissions

Managing sync rules is part of configuring HubSpot and needs Global integrations (core.institutions.global_integration_settings), see Integrations. The scope pickers list the programmes and courses visible to the staff member editing the rule.