NexaLink integrations: where your contacts go next
A digital business card is only useful if the contacts it captures reach the system you already run on. Here is exactly what connects today, what each connection does, and which plan it needs — including the things we have not built, which are named rather than hidden.
The short answer
Salesforce sync is self-serve today on every paid plan — authorize it from Integrations in the app and captured contacts are pushed across, deduped by email. It is a one-way push out of NexaLink, not a two-way mirror.
For anything else, the REST API lets you pull contacts into your own system on your own schedule. It is a Business and Agency feature. MCP — running your contacts from Claude or ChatGPT — works on every plan, including free.
What we do not have: Zapier, and a two-way CRM sync. HubSpot and Zoho connectors are written but not switched on for self-serve. Buy on what is live, not on this paragraph's second half.
What connects today
Status is not a marketing word here: a connector is live only when you can authorize it yourself. Inside the app, a tile that says Connect is live and one that says Coming soon is not.
| What it does | Plans | Status | |
|---|---|---|---|
| Salesforce | One-way push of your NexaLink contacts into Salesforce as leads, deduped by email | Every paid plan | Live — self-serve |
| REST API | Pull contacts into your own CRM or database, with an incremental delta and deletion tombstones | Business and Agency / White-Label | Live |
| MCP (Claude, ChatGPT, Cursor) | Read and edit your card, search contacts, add notes and follow-ups from inside an AI assistant | Every plan, including free | Live |
| Connects your own LinkedIn profile for personalization — not a connection importer | Every plan, including free | Live | |
| Apple & Google Wallet | Generates a wallet pass for your card so people can keep it on their phone | Business and Agency / White-Label | Live |
| HubSpot | Same connector engine as Salesforce — contact push, deduped by email | Every paid plan when enabled | Built, not switched on (unverified figure) |
| Zoho CRM | Same connector engine as Salesforce — contact push, deduped by email | Every paid plan when enabled | Built, not switched on (unverified figure) |
| Zapier | Would route contacts to other tools | — | Not built (unverified figure) |
* HubSpot and Zoho are implemented against the same provider interface as Salesforce, but self-serve connect stays hidden until their OAuth credentials are configured in production — so you cannot start a flow that would fail halfway. Treat them as unavailable when planning a purchase. Zapier has no implementation at all. Checked 2026-08-09.
CRM sync, precisely
The honest shape of it, so nothing is a surprise after you pay.
It is one-way, out of NexaLink
Contacts you capture — scanned cards, lead-capture forms, contacts you add by hand — are pushed to your CRM. Your CRM's existing records are not pulled back into NexaLink. If you were expecting a two-way mirror, this is not that, and no amount of configuration makes it that.
Self-serve, no call
You click Connect, authorize NexaLink on the provider's own consent screen, and syncing starts. There is no onboarding fee and no implementation call. You can disconnect from the same screen, which revokes the token at the provider.
Deduped, and safe to re-run
Records are matched on email, and every contact we have already pushed is tracked with a content hash — so an unchanged contact is skipped rather than written again. Syncing twice does not create duplicates. You can trigger a sync on demand, and a background queue retries anything that failed with an increasing backoff instead of hammering your CRM.
What actually crosses
Name, email, phone and mobile, company, job title, website, LinkedIn, city, state, country, your notes, tags and the capture source. In Salesforce each contact lands as a Lead with a LeadSource of NexaLink, so it is filterable from day one. Deletions propagate: remove a contact in NexaLink and the Salesforce connector deletes the Lead it created, rather than leaving an orphan behind.
Who can turn it on
Every paid plan — Solo, Team, Business, Agency / White-Label. The free plan is the only one gated. Seats are people and cards are brands, and neither limit affects CRM sync: Solo is 1 seat with 5 cards and still syncs.
The REST API
For the case a connector cannot cover: your own CRM, your own data warehouse, a homegrown ops tool. Base URL https://nexalink.co/api/v1. Available on Business and Agency / White-Label.
| Endpoint | What it does | Scope |
|---|---|---|
| GET /v1/me | Your plan, limits, the token's scopes and whether API access is on — so a 403 is diagnosable without a support ticket | any valid token |
| GET /v1/contacts | Incremental contact pull: updated_since for a delta, cursor pagination, a sync token to checkpoint on, and tombstones so you learn about deletions | contacts:read |
| POST /v1/contacts | Create a contact | contacts:write |
| GET /v1/contacts/{id} | Fetch one contact | contacts:read |
| PATCH /v1/contacts/{id} | Update one contact | contacts:write |
| POST /v1/contacts/{id}/notes | Append a note to a contact | contacts:write |
Authenticate with a personal access token as Authorization: Bearer …, minted in Settings and shown once. Tokens can be scoped; an unscoped legacy token has full access. Pages return up to 500 contacts. Rate limits are per token per day — unlimited on the Premium-entitlement plans that can use the API. Private scanned-image URLs are never returned.
The part most sync clients get wrong
A delta feed that only lists live records silently accumulates ghosts on your side. GET /v1/contacts with updated_since returns deleted contacts too, carrying a status other than active — drop those from your copy and the two systems stay honest. This is the same code path our own connectors use, so your integration cannot drift from ours.
MCP — the integration on every plan
The REST API is gated because it is a machine-to-machine sync channel. MCP is not: connect Claude, ChatGPT, Cursor or any MCP client to your account and ask it to edit your card, find a contact, write a follow-up or pull everyone you met at an event. It runs as your own account, on every plan including free, and it is the reason a free user still gets AI over their contacts — they bring their own assistant.
Which plan you need
One payment, no per-seat billing. Seats are people; cards are brands.
| Solo | Team | Business | Agency / White-Label | |
|---|---|---|---|---|
| Price | $59 once | $249 once | $549 once | $1,199 once |
| Seats (people) | 1 | 10 | 50 | 250 |
| Cards (brands) | 5 | 5 | Unlimited | Unlimited |
| CRM sync (Salesforce) | Yes | Yes | Yes | Yes |
| REST API | No | No | Yes | Yes |
| MCP / AI assistants | Yes | Yes | Yes | Yes |
| Wallet passes | No | No | Yes | Yes |
| Contact export (Excel) | Yes | Yes | Yes | Yes |
| Custom domain | No | No | Yes | Yes |
MCP is available on the free plan too, so this row is a formality. CRM sync is on every paid plan; the REST API is Business and Agency / White-Label only. Custom domains are also Business and Agency / White-Label — Solo and Team do not include one, and no plan white-labels the mobile apps. Agency / White-Label adds client workspaces on a shared 250-seat pool, and creating one costs no seats. All prices in USD. NexaLink bills in USD, so a Canadian buyer is charged the USD amount.
Contact limits do not interact with any of this: paid plans store an unlimited number of contacts, while free stops at 25.
Common questions
Does NexaLink sync contacts to my CRM?
Yes, for Salesforce. You authorize it yourself from Integrations inside the app — no sales call and no setup fee — and captured contacts are pushed to Salesforce, deduped by email. It is a one-way push from NexaLink to your CRM; it does not pull your CRM records back into NexaLink. HubSpot and Zoho connectors are built on the same engine but are not switched on for self-serve yet.
Which plans include CRM sync?
Every paid plan. Solo and Team map to the Pro entitlement and Business and Agency to Premium, and CRM sync is enabled on both. Only the free plan is gated — it returns upgrade_required if you try to connect.
Do you have a public API?
Yes. A REST API at https://nexalink.co/api/v1 with contact read, create, update and note endpoints, keyset pagination, an updated_since delta and deletion tombstones so an external system can stay in sync. It is available on Business ($549 once) and Agency ($1,199 once) — the two Premium-entitlement plans.
How do I authenticate against the REST API?
With a personal access token you mint yourself in Settings, sent as an Authorization: Bearer header. Tokens can be scoped to contacts:read, contacts:write or sync:trigger, and the raw token is shown only once when it is created. OAuth access tokens are for MCP clients only and are rejected by the REST API.
Can I use Zapier with NexaLink?
Not yet — there is no Zapier integration today and the tile inside the app is a teaser, not a working connector. If you need to route contacts into another tool now, the REST API on Business or Agency is the supported path, and MCP works on every plan.
Does the LinkedIn integration import my connections?
No. LinkedIn connects your own profile — name, email and picture — for personalization. Bulk import of your LinkedIn connections is not built, and LinkedIn's API does not offer it to apps like ours. It is free on every plan.