Introduction
Baton’s Hubspot integration allows users to automatically import projects into their Baton Workspace, and users can choose and define a field mapping to keep data in sync between Baton and the source Hubspot object.
In order to turn this feature on, a workspace admin will need to connect a Hubspot account to their workspace
Clicking on Connect Hubspot will take users to a Hubpost login screen (if they are not already logged in to Hubspot), and upon login, the following authorization screen will be shown:
After clicking on Connect app, users will be redirected to the Baton connected apps page.
Configuration
By default, Hubspot Deal objects will be used as source object for automatic project import. Users can change this to any other standard CRM object (i.e., Contact, Company, Product, Line Item, Ticket, Conversation). Custom objects are not supported for the initial release of the integration, but support for these objects will be added in a future release.
In order to automatically import projects into Baton, an import rule must be defined. Any field of type enumeration (that is, a select field with multiple options) or boolean can be chosen.
Additional import prerequisites can be added if users want to filter out which objects are imported into Baton. It is important to note that all prerequisites must be met at the time the object transitions into a state where the import rule is met, otherwise it will not trigger a project import.
By default, Baton creates one project per source object record — per Deal, per Company, or whichever object type you've configured as your source object. If your team runs a separate project for each product, service tier, or line item on a single record, Source Properties lets Baton create one project per value of a HubSpot property instead.
For example, if your source object is Deal and a Deal has a "Products" field with the values Onboarding, Migration, and Training, turning on Source Properties for that field creates three separate Baton projects from that one Deal — one per product. The same works for any other source object: one Company with a "Regions" field could fan out into one project per region, for instance.
To set this up:
Go to Settings > Connected Apps > HubSpot.
Under Source Object, turn on Use [Object] Properties as source object (where [Object] is whichever object type — Deal, Company, etc. — you've set as your source object). Turning this on doesn't create anything by itself — you'll need to add at least one property below before new projects can be imported this way.
Click Add [Object] Property and choose the HubSpot property whose values should each get their own project (for example, a dropdown or multi-select field).
You can add more than one property. Each one is evaluated independently, so a single source object record can fan out into project sets driven by "Products" and "Region," for instance, side by side.
A few things to know:
Multi-select fields work too. If a property can hold more than one value (like a multi-checkbox field), Baton creates one project for each value present on that record — not one project with all the values combined.
No values, no project. If a given record doesn't have any value set for a configured property, no project is created from that property for that record (its other configured properties, or the default import rule, are unaffected).
Turning it off is safe to reverse. Disabling the toggle stops new fan-out projects from being created and Baton goes back to creating a single project per source object record — but your configured properties are kept, so re-enabling it later restores the same setup. Note: any Field Sync rules (see below) scoped to a specific property are deleted when you turn this off, since they no longer apply to anything.
This works alongside Template Mapping, Project Lead, and Field Mapping — see the updated sections below for how each of those can now target a specific property's projects.
Field Mapping
Users can choose what fields will be synced between Baton projects and the configured Hubspot source object. This sync will be bidirectional, with the exception of Hubspot read-only fields. These fields are labeled with a (read-only) tag.
Baton custom fields of type text, numeric, boolean and date are currently supported. Support for Dropdown (single select and multi-select) will be added in the future.
Scoping a field sync to a specific property
If you've set up Source Properties so that a single source object record creates several projects, you can control which project(s) a given field sync applies to using the Applies To setting on each Field Sync row.
All projects (default) — this sync applies to every project created from the record, regardless of which property drove its creation. This is what you want for fields that should be the same across all of a record's projects (like a shared Description).
Scoped to: [Property] — this sync only applies to the project(s) created from that specific property's values. Use this when a field's meaning is different depending on which slice of the record a project represents.
Bidirectional sync and multiple projects: If bi-directional sync is turned on, edits made in Baton are pushed back to HubSpot as usual. When several projects share the same source object record (via Source Properties), an edit made in any one of those projects is pushed to the shared record in HubSpot, and from there automatically applied to every sibling project that shares that field sync — so all of a record's projects stay in sync with each other, not just with HubSpot.
Template mapping and Default Project Lead
Similar to our Salesforce integration, a default project lead can be configured for all projects imported from Hubspot, and template mapping rules can be defined based on certain conditions.
Template Mapping
Baton can automatically apply a template to a project when it's imported from HubSpot, based on a picklist value or an exact match of a numeric or text field on your source object.
You can configure more than one source field for Template Mapping. Each one is evaluated independently — Baton checks every configured field against the incoming record, and applies whichever template(s) match.
Important: Template Mapping never creates a project on its own. It only decides which template to apply to a project that's already being created — either the single default project for that record, or one of the fan-out projects created by Source Properties (see above). If more than one Template Mapping rule matches the same project, all matching templates are applied to that one project rather than creating separate projects.
Assigning a Project Lead from HubSpot data
In addition to setting a single default project lead for all HubSpot-imported projects, you can configure Baton to assign the project lead based on a HubSpot field's value on your source object — for example, assigning leads by owner, region, or a custom property.
You can add more than one project lead source field. Each is evaluated on its own, so different projects (including sibling projects created by Source Properties) can get their project lead from different fields.
If a record's value for a configured field doesn't match any of your configured assignment rules, the project falls back to your workspace's default project lead.
Client Company
If the source object has an associated Company, it will be automatically imported into Baton upon project import. Client companies imported from Hubspot will be shown with a hubspot icon next to their name in Client Directory
Existing Clients in Baton can also be linked to Hubspot Companies by using the Hubspot Connection option:
Projects imported from Hubspot will be shown with an icon next to the their name. Clicking on the icon will open the object in Hubspot in a new tab.
Manual object association
In addition to automatic import, existing Baton projects can also be manually associated to Hubspot objects. Using the Hubspot Object select in the Project Details Integrations page, users can look by ID or name for the object this project will be connected to. All objects will be listed as available for manual connection, even if they don’t meet the import criteria defined for automatic import. Upon selection, users will be shown a table with the existing data both in Baton and in Hubspot for the mapped fields (as defined in the workspace settings page), and will be able to choose the direction for initial data sync
NOTE: Choosing an object that is already associated to a Baton project will show a warning indicating a connection to that object already exists:
Disconnecting HubSpot removes the connection and clears your Field Mapping, Template Mapping, Project Lead, Import Rule, and Source Property configuration for that workspace. Projects already created from HubSpot are not affected or deleted — reconnecting later starts fresh, with sync settings back at their defaults (including Source Properties, which start off on a new or reconnected integration).