Connect other tools

Connect HubSpot.

Who can do this: Owners and admins.
Where in the app: Integrations, then HubSpot

In short

You will have sent your first consented lead to your own HubSpot account. The sync is one way: 1Namecard writes to HubSpot and never reads contacts back.

Steps checked 15 October 2026

Connect and set up.

Step 1.
In HubSpot, create a private app with type Private. HubSpot changes the menu names from time to time. Look for Legacy apps or Private apps in its settings. Name the app 1Namecard.
Step 2.
On the app's Scopes tab tick crm.objects.contacts.read, crm.objects.contacts.write, crm.objects.companies.read, crm.objects.companies.write, crm.objects.deals.read, crm.objects.deals.write, crm.objects.owners.read, crm.schemas.contacts.read and crm.schemas.contacts.write. Create the app and copy the access token. It starts with pat-.
Step 3.
In 1Namecard open Integrations and press Connect HubSpot. The button reads Manage HubSpot once a token is saved.
Step 4.
Under Connect, paste the token into Private app token and press Save token. Only its last four characters are shown afterwards.
Step 5.
Press Test connection. A pass says Connected to HubSpot portal and your portal number. A missing scope is listed by name.
Step 6.
Under Custom properties, press Create custom properties once. It adds nine contact properties in a group called 1Namecard and leaves existing ones alone.
Step 7.
Under Setup, choose a Deal pipeline, or No deals (contacts and notes only). Then pick a HubSpot stage for each lead stage under Deal stage for each lead stage: New, Contacted, Qualified, Meeting, Won and Lost. A row left at Keep the deal where it is does nothing. Changing the pipeline clears the rows.
Step 8.
Set Create a deal to When a meeting is requested or When the lead reaches Qualified. Choose a Default owner. Leave Who is sent on Only leads who ticked the consent box unless your legal basis allows more. Leave Set the marketing contact status for opt-ins unticked, because it can count against your HubSpot marketing contacts.
Step 9.
Tick Send leads to HubSpot and press Save setup.
Step 10.
Under Owners, press Auto-match by email. It links each member to the HubSpot user with the same e-mail address. Pick an owner by hand for anyone it misses and press Save. Hand-picked links are never overwritten.

What is sent.

A submitted card form creates or updates a contact by e-mail address, a company by domain and a note. A meeting request adds a meeting. A deal is created once per company and event, not once per lead. Stage and owner changes follow. IP addresses, browser details and the internal note are never sent. With the consent setting, a lead without the ticked box is marked no consent on its HubSpot panel and is skipped without an error.

Read the log and retry.

Log lists every job as pending, done, failed or dead. A temporary problem is retried by itself, waiting 2, 4, 8, 16, 32 and then 60 minutes. A refusal, such as a missing scope, stops as failed. Fix the cause and press Retry on the row, or Retry all failed. Backfill queues up to 500 qualifying leads that were never sent, oldest first, and needs Send leads to HubSpot on. Each lead has a HubSpot panel with Sync now.

Common questions.

Does it read anything back from HubSpot?

No. It is one way. Changes you make in HubSpot do not change 1Namecard. It reads only your pipelines, properties and owners, so that setup and owner matching can work.

What does Disconnect do?

It deletes the saved token and turns sending off. Your setup and owner links are kept, so connecting the same HubSpot account again picks up where it stopped.

A job failed with a missing scope. What now?

The message names the scope. Add it to the private app in HubSpot, which keeps the same token, then press Retry in the log.

All help articles Ask us