This page contains the setup guide and reference information for the HubSpot integration.

HubSpot is a customer relationship management (CRM) platform widely used by event organizers and associations to manage Contacts, Companies, and event registrations. The Swapcard integration imports HubSpot Contacts as Swapcard People (Attendees, Speakers) and HubSpot Companies as Swapcard Exhibitors, scoped to a specific event via a custom Swapcard Event object in HubSpot.

Before connecting Swapcard, your HubSpot account needs two pieces of configuration:

The Swapcard integration uses a HubSpot custom object called Swapcard Event to scope event data. Contacts associated with a Swapcard Event record are imported as Swapcard People, and associated Companies are imported as Swapcard Exhibitors.

Log in to your HubSpot account and click the Settings gear icon in the top navigation bar.

In the left sidebar, go to Data Management → Objects → Custom Objects.

Click the Create custom object button.

Fill in the following fields, then click Create:

Important: the Internal name must be swapcard_events exactly. The HubSpot API exposes this object as p_swapcard_events, which is what the Swapcard sync queries.

From the Swapcard Events object view, select the Associations tab.

Create the following two associations:

Use the Search HubSpot bar to find Swapcard Events and open the object.

Click Add swapcard events, then select Create new.

Enter the name of your event, then click Create Swapcard Event. This record represents your event in HubSpot — Swapcard will list it when you connect the integration and ask you to pick which event to sync.

Open the event record. From this view, you can associate Contacts and Companies to the event.

Contacts associated with the event will be imported as Swapcard People (Attendees, Speakers). Companies associated with the event will be imported as Swapcard Exhibitors. Records that are not associated with the Swapcard Event record are ignored by the sync.

Swapcard authenticates to HubSpot using a Private Legacy App access token.

In the HubSpot left sidebar, select Development.

From the Development menu, select Legacy Apps.

On the Create Legacy App view, select Private.

On the Basic info tab, fill in:

Select the Scopes tab and click Add new scope. Add read scopes for the following objects:

Without all three read scopes the integration cannot list events, contacts, or companies and the connection test will fail.

Click Create app, then Continue creating to confirm.

Go to the Auth tab on the Swapcard-Access app, click Show token, then Copy. This token is what you will paste into Swapcard Studio in the next section.

Important: treat this token like a password. It grants read access to Contacts, Companies, and Custom Objects on your HubSpot account.

Your HubSpot event has been successfully linked with your Swapcard event.

You have the flexibility to adjust your integration settings according to the specific data requirements. It's crucial to highlight that the synchronization will only begin when you manually start the integration process and finish the necessary mapping.

The HubSpot integration supports the following sync modes:

On the first sync (no previous successful sync), Swapcard fetches every Contact and Company associated with the configured Swapcard Event record. On subsequent syncs, only records modified since the last successful sync are fetched, using HubSpot's hs_lastmodifieddate / lastmodifieddate filters.

In addition, when HubSpot webhook subscriptions are enabled for contact.* and company.* events, Swapcard processes those updates in near real-time — each notified record is re-fetched, verified to still be associated with the Swapcard Event, and re-synced.

This integration supports two streams: Contacts and Companies, scoped to a single Swapcard Event custom object record on the HubSpot side.

Only Contacts and Companies that are associated with the selected Swapcard Event record in HubSpot are imported. Records without that association are ignored.

The HubSpot integration does NOT capture deletions. When a record is deleted in HubSpot (or unassociated from the Swapcard Event), it will not be removed from Swapcard. Deleted records must be MANUALLY removed from Swapcard.

The HubSpot integration uses the HubSpot record ID (hs_object_id) as the primary identifier for both Contacts and Companies. This value is stored in the Client Id field on the People or Exhibitor record on the Swapcard side.

Each stream exposes a set of standard fields plus all custom HubSpot properties of supported types. Supported property types are: string, number, date, datetime, bool. HubSpot properties whose label contains an underscore are excluded from the field picker (these are typically internal / system properties).

These fields come from the HubSpot Contact properties. Any custom property defined on the Contact object in HubSpot (matching the supported types above) is automatically available in the Swapcard mapping UI.

Default Swapcard mappings:

These fields come from the HubSpot Company properties. Any custom property defined on the Company object in HubSpot (matching the supported types above) is automatically available in the Swapcard mapping UI.

Default Swapcard mappings:

The HubSpot integration only imports records associated with the selected Swapcard Event custom object record. Contacts and Companies that exist in HubSpot but are not associated with that event will not be imported, even if they otherwise match a sync filter.

Because the HubSpot Search API cannot filter associated records by last-modified date in a single call, incremental syncs first fetch all records modified since the last sync and then verify, one record at a time, whether each is still associated with the Swapcard Event. On accounts with very high modification volume this verification step can be slow.

The integration validates credentials by calling the p_swapcard_events endpoint. If the Custom Objects read scope is missing on the Private Legacy App, the connection test will fail even when Contacts/Companies scopes are present.

Please be aware that any enhancements to this integration, which encompass any requirements not covered by the existing integration state, will be subject to custom development processes and associated costs.