The gap between collecting contacts and working them
You leave a conference, a trade show, or a busy site visit with a phone full of new connections. Some you’ve swapped details with via a QR scan or an NFC tap. Others handed you a physical card that you’ve since scanned with your phone. Either way, those contacts are sitting somewhere — and they are not yet in your CRM.
That gap is where deals go quiet. The follow-up that should happen on Tuesday gets pushed to Thursday, then forgotten entirely. A digital business card Zapier CRM integration is the mechanism that closes that gap automatically, moving a new contact from your BONKT profile into Salesforce or HubSpot the moment they save your details — without you touching a keyboard.
This post walks through exactly how that works: the trigger, the field mapping, and what the record looks like when it lands in your CRM. It also explains what BONKT is and is not in this workflow, so you set it up with the right expectations.
What BONKT does — and where it stops
BONKT is the capture layer. When someone scans your QR code, taps your NFC card, or opens your shared link, your contact profile loads in their browser. They do not need an app, an account, or anything installed on their device. They see your details and can save them straight to their phone’s contacts with a single tap.
That save event — and the profile view itself — generates data that BONKT records. What BONKT does not do is manage a sales pipeline, score leads, or log call activity. It is not a CRM, and it does not try to be one. Its job is to make sure the person you just met has your details accurately, and that you have a record of the interaction.
Your CRM — whether that is Salesforce, HubSpot, or another platform — is where the pipeline lives. The integration question is simply: how do you get the contact from one system to the other, reliably, without manual data entry?
The answer is Zapier or Pabbly Connect. BONKT connects to both. Pabbly Connect alone gives access to over 1,000 apps. See the full features overview for the current integration landscape.
Understanding the trigger
In Zapier’s language, every automation has a trigger — the event that starts the chain. For a digital business card Zapier CRM integration built on BONKT, the trigger is an action taken on your card: a new contact saved, a form submission from your profile, or a lead capture event depending on how your card is configured.
BONKT surfaces contact data through its Contact Management Centre. When someone saves your card to their contacts, that interaction is logged. Zapier watches for new entries in that log and fires the automation when one appears.
A few things worth knowing before you build the Zap:
- The trigger fires on the BONKT side. The person sharing the card — you — is the BONKT account holder. The person receiving it never needs a BONKT account. They tap or scan, save, and that is the end of their involvement.
- Zapier requires you to authenticate your BONKT account during setup. This is a one-time step and uses OAuth, so your credentials are not stored in the Zap itself.
- Test the trigger with a real scan before you map fields. A test contact gives you a concrete data object to work with, which makes the field-mapping step much cleaner.
Field mapping: what arrives and where it goes
Field mapping is where most integrations break down, not because the tools are difficult but because people skip the planning step. Before you open Zapier, write down what fields your CRM contact record requires — typically first name, last name, email, phone, company and job title — and check which of those your BONKT card actually collects.
BONKT profiles support a wide range of contact fields: name, job title, company, phone numbers, email addresses, physical addresses, website URLs and custom fields. The Save to Contacts feature structures this data in a standard vCard format, which means field names are predictable and map cleanly to CRM schemas.
In Zapier, the mapping step looks like this:
- Trigger output field: the data coming from BONKT (e.g. “contact.first_name”)
- Action input field: the corresponding field in your CRM (e.g. “First Name” in HubSpot or “FirstName” in Salesforce)
Map every required CRM field. Leave optional fields blank rather than mapping them to mismatched data — a blank field in a CRM record is far easier to fix than a field populated with the wrong value.
Handling duplicates
Most CRMs have a native duplicate-detection rule based on email address. Before your Zap creates a new contact, consider adding a search step: “Find Contact in HubSpot by email”. If a record exists, route the Zap to update the existing record rather than create a second one. If no record exists, proceed to creation. This two-branch structure adds about three minutes to the build and saves a significant amount of cleanup later.
Adding context the card cannot carry
Your BONKT card tells the CRM who the contact is. It does not tell the CRM where you met them. Add a Zapier “Formatter” step before the CRM action and use it to inject a static note — something like “Source: BONKT card scan, [event name]” — into the contact’s notes or lead source field. That context is worth having when you review the pipeline three weeks later and cannot remember which conference a name came from.
The same logic applies with Pabbly Connect
If you are already using Pabbly Connect rather than Zapier, the architecture is identical: trigger on a BONKT contact event, map fields, create or update a CRM record. Pabbly Connect supports Salesforce and HubSpot natively, and its workflow builder uses the same trigger-action-filter model. The practical difference is pricing — Pabbly Connect charges per workflow rather than per task, which may suit teams running high-volume automations.
For teams on BONKT Pro or BONKT Unleashed, the integration capability is the same regardless of which automation platform you choose. The business integration page has more detail on supported platforms.
What the record looks like when it lands
Done correctly, a new contact arrives in your CRM within seconds of the card being saved. The record contains the structured contact fields from the BONKT profile, the source note you injected via the Formatter step, and a creation timestamp from Zapier. In HubSpot, it will appear in your Contacts view with a lifecycle stage of “Lead” by default — you can override this in the Zap’s action step if your pipeline uses a different entry stage.
In Salesforce, the record lands as a Lead object unless you map it directly to a Contact. For most sales workflows, Lead is the right entry point — it sits outside the account hierarchy until you qualify and convert it.
From that point, the contact is in your CRM and your normal follow-up process takes over. The automation’s job is finished.
What about physical cards you receive?
The workflow above handles contacts you collect when someone receives your BONKT card. But you will still receive physical cards from people who do not use a digital platform. BONKT’s AI Paper Card Scanner handles this: photograph the card, and BONKT extracts the contact fields. Once the contact is in BONKT’s Contact Management Centre, the same Zapier automation can push it to your CRM using the same trigger and field map.
Note that scanned card images are processed by OpenAI as part of the extraction step — this is disclosed in BONKT’s privacy policy, and worth knowing if your organisation has data-handling policies that cover AI sub-processors.
Before you build: a quick checklist
A digital business card Zapier CRM integration is a straightforward build, but a few minutes of preparation prevents the most common failure modes:
- Confirm which BONKT plan you are on. Bulk card creation and team management features are available from BONKT Pro upward; the free tier has limited analytics and no custom domain.
- Check your CRM’s required fields before mapping. A Zap that fails on a missing required field will not create the record and will not tell your contact anything went wrong.
- Test with a real scan, not a sample record. Zapier’s sample data sometimes omits optional fields that your live data includes.
- Set up error notifications in Zapier. A failed Zap is silent by default — turn on email alerts so you know if the automation stops working.
- Review the duplicate-handling logic quarterly. CRM schemas change, and a field rename can break a mapping silently.
The capture layer and the pipeline layer
BONKT’s role in this workflow is specific: it is where the contact interaction happens. The QR code, the NFC tap, the saved vCard — these are the moments where someone decides to keep your details. Saving to contacts is frictionless for the recipient because they never need an account or an app. That frictionlessness is what makes the capture reliable enough to automate from.
The CRM is where the relationship is managed after that moment. Zapier or Pabbly Connect is the bridge between the two. None of these tools replaces the follow-up call or the actual conversation — they just make sure the information from the first meeting is in the right place before the second one happens.
If you are not yet using BONKT, the free tier lets you build a card and test the sharing experience at no cost. The benefits overview covers what is available across plans. For teams, the plans page has the current pricing — BONKT Pro is AUD $10.99 per user per month, GST inclusive, with no lock-in contract.
