Connect
Send trade show leads to HubSpot.With owner, stage and consent.
A one way sync from 1Namecard to your own HubSpot account. Consent-gated by default, with a log you can retry from.
1Namecard lead
Mia Fischer
Harbourline Freight
Placement dw27-badge
Consent given
- Synced
Contact
Mia Fischer, with placement, score and stage
- Synced
Company
Harbourline Freight, found by e-mail domain
- Synced
Deal
Harbourline Freight, DataWorks Europe 2027
Stage: Meeting
- Synced
Note
Consent wording and score reasons
- Synced
Meeting
Thursday 10:30, stand time
One way, from 1Namecard to your own HubSpot, for leads who ticked the consent box. Nothing is read back.
In short
The 1Namecard HubSpot integration is a one way sync that pushes every lead and meeting request from your digital business card into your own HubSpot account. It upserts the contact by e-mail address, finds the company by domain, opens one deal per company and event, and adds a note and a meeting. Only consented leads are sent by default. Nothing is read back.
Last updated
What it does.
Upsert contacts by e-mail address.
Each lead creates or updates one contact with name, phone, job title and nine
nw_properties: placement, score, band, card, event, consent text and time, actions and stage.Find companies by e-mail domain.
The company is found by the lead's e-mail domain, or created. Personal mail domains such as gmail never create one.
Open one deal per company and event.
Under Create a deal pick the trigger: a meeting request, or a lead reaching Qualified. Later stage changes move the deal through the stage map you set.
Write a note and a meeting per booking.
A card form adds a note with the actions taken. A booking adds a meeting at the right UTC time, and its outcome follows the status in 1Namecard.
Match owners by e-mail.
Auto-match by email links each member to the HubSpot user with the same address. Hand-picked links are never overwritten. The contact owner is the lead's owner, else the card's, else your default.
Gate the sync on consent.
Who is sent defaults to consent only, checked again when the job runs. Marketing contact status stays off unless you switch it on, because it can count against your HubSpot plan.
Retry, backfill and delete.
The Log has Retry and Retry all failed. Backfill queues earlier leads, up to 500 per click. A delete request for one e-mail address is passed on to HubSpot.
5 to 6
HubSpot requests for one lead
1
deal per company and event
500
leads per backfill click
How it works in three steps.
Step 01
Create a private app in HubSpot.
As a super admin, open Settings, Integrations, Legacy apps. Tick the contacts, companies, deals and owners scopes and copy the token.
Step 02
Paste the token and run setup.
Under Integrations, HubSpot: Save token, Test connection, Create custom properties, then pick a pipeline and map stages.
Step 03
Switch on Send leads to HubSpot.
New leads flow at once. Press Backfill for leads from before you connected.
Who it is for.
Sales operations
You own HubSpot and want show leads in it with a consent record.
Reps
You find your lead in HubSpot with the note and meeting.
Exhibitor marketers
You report on placement and show from properties.
Limits by plan.
- Included: Every plan has the sync. You need your own HubSpot account and a private-app token.
- Included: One lead costs five to six HubSpot requests. Rate-limit answers are retried. Backfill is capped at 500 per click.
What it does not do yet.
- Not included: Nothing is read back from HubSpot. A change there does not change a lead here.
- Not included: The sync is built to HubSpot's documented API and tested against a mock of it, not yet a live portal. We recommend a sandbox portal first.
- Not included: Salesforce, Pipedrive, Microsoft Dynamics 365 Sales and Zoho CRM native integrations are decided and in development. See the roadmap. Until then use signed webhooks or the API.
- Not included: Two leads from a new company domain in the same second can, rarely, create a duplicate company.
What reaches HubSpot, and when.
| Event | In HubSpot |
|---|---|
| Visitor sends the card form | Contact by e-mail, company by domain, a note |
| Visitor requests a meeting | The same, plus a meeting and a deal if you chose that trigger |
| Lead reaches Qualified | A deal, if you chose that trigger |
| Stage or owner changes | The stage property or owner, and the deal moves per your map |
Consent and privacy stay attached to the contact.
The wording the visitor saw and the time they agreed are stored in nw_consent_text and nw_consent_at. IP address, browser details and the internal note are never sent. Delete all data for this email also asks HubSpot, once, to delete the contact. If HubSpot is disconnected or the token no longer works, that request does not happen.
Read the log when a lead does not appear.
- pending: waiting for its turn or the next try.
- done: sent. The lead page links to the contact.
- failed: HubSpot refused it, for example a missing scope, which the message names. Fix it, then Retry.
- dead: eight tries failed. Retry starts again.
Temporary problems retry by themselves after 2, 4, 8, 16, 32 and then 60 minutes.
Questions about this feature.
Is the HubSpot sync two way?
No. It is one way, from 1Namecard to HubSpot, so changes in HubSpot never overwrite anything here.
What do I need in HubSpot?
A super admin who can create a private app, and room for nine custom contact properties. The token is stored encrypted.
Does it send leads who did not give consent?
Not by default. An owner or admin can switch to every lead, which is only right if your legal basis allows it.
Has it been tested with a live HubSpot portal?
It is built to HubSpot's documented API and tested against a mock of it. Try a sandbox portal with a few test leads first.