# Salesforce business card scanner: scans into your pipeline
Salesforce will not chase the cards in your bag. Here is how to choose a scanner for it, the exact Zapier route from a scan to a lead, and what a lead record demands before it will save.
- Category: Integrations
- Reading time: 7 min read
- HTML: https://www.connectmachine.ai/blog/business-card-scanner-salesforce-zapier/
A Salesforce business card scanner has exactly one job: turn the card in your hand into a lead record that saves without an error. Most of them get the reading part right and the saving part wrong, because Salesforce asks for fields a business card has never carried.
Every rep has the same drawer. A conference badge, a hotel pen, and forty cards from people who were interested at the time. Below is the route that empties it without typing, where ConnectMachine scans the card and a Zap creates the Salesforce lead, plus the parts of a lead record that will still fail validation at 11pm if you skip them. The last section covers the version of this that matters most: capturing a whole event's worth of leads rather than one card at a time.
## The short answer
Open the public Create Salesforce leads from new ConnectMachine contacts template on Zapier, connect both accounts, map the fields Salesforce requires, run one test, and turn the Zap on. From that point, every contact added in ConnectMachine, including the ones you create by scanning a card, arrives in Salesforce as a lead without you retyping anything.
Two Salesforce-specific things decide whether this works. The template writes leads rather than contacts, and that choice quietly shapes your reporting for months. And Salesforce is the strictest destination on the list about what a record needs before it will save, so the mapping step is where the time actually goes.
[Open the Salesforce Zap template](https://zapier.com/apps/connectmachine/integrations/salesforce/255732614/create-salesforce-leads-from-new-connectmachine-contacts)
## Choosing a business card scanner for Salesforce
Search for the best business card scanner for Salesforce and you get a list of apps with no way to tell which problem each one solves. There are really only four routes, and the right one depends on how many cards there are and on whether Salesforce is the only place the person needs to reach. Ask your admin what is already installed before you buy anything: what a Salesforce org can do varies by edition and by what came from AppExchange, so nobody outside your company can tell you what you already have.
### A CSV import, for a backlog
A stack of cards from an event three weeks ago is a one-off job, not an automation. Read the batch in the browser with the free bulk business card scanner, which handles 10 cards per batch and exports CSV, Excel, or vCard without an account, then load it with Salesforce's own import tooling. Building a Zap to solve a problem that ends today is wasted effort.
### An AppExchange scanner, when Salesforce is the whole world
Card scanners that install into the org write leads directly and never leave Salesforce. That is the shortest path when every person you meet is a sales record and your whole team lives in the CRM. Check the pricing model before you commit, because most are priced per user per month and per scan credit, and check what happens to the data if you ever uninstall.
### ConnectMachine plus Zapier, for the steady drip
Cards arrive in ones and twos all year, and that is the flow worth automating. Scan on the spot, keep the notes and the where you met detail attached, and let the Zap put the lead in Salesforce before you have left the building. The capture layer sits outside the CRM, so the same scan can also reach Slack or a follow-up sequence without doing the work three times.
### Nothing at all, when the card is not a lead
The route people skip. Not everyone you meet belongs in the pipeline, and filing them all as leads is how a conversion rate stops meaning anything. Capture them first, decide afterwards which ones Salesforce should see.
## Decide first: lead or contact
This is the decision that makes or breaks the setup, and it comes before any of the Zapier steps. Salesforce keeps unqualified people as leads and qualified ones as contacts attached to an account. The published template creates leads, which suits the way most people collect cards: you met someone, you do not yet know whether there is a deal, and the lead object is exactly the holding pen Salesforce built for that.
### Keep leads if the cards are prospects
Conference floors, trade shows, and cold introductions all produce people your team has to qualify. Leaving them as leads keeps them out of your account hierarchy until someone decides they belong there, and it lets Salesforce's conversion flow do the promotion properly.
### Switch the action if the cards are known relationships
Partners, vendors, and existing customers are not leads and filing them as such pollutes your reports. Swap the Salesforce step in the template for Create Contact, or add a Zapier filter so only the cards worth qualifying take the lead path.
Get this wrong and you find out three months later, when your lead conversion rate is meaningless because half the records were never leads. Decide it once, at the start, and the rest of the setup is mechanical.
## What you need
- A Salesforce org whose edition allows API access, since that is how Zapier writes into it. If you are not the admin, confirm this before you build rather than debugging a failed connection later.
- Permission to create leads, plus a note of which fields your admin has made required and which validation rules run on save.
- A Zapier account. Check your own plan first: Zapier prices some CRM connections above its free tier, and Salesforce is the kind of app that policy applies to.
- Zapier access on your ConnectMachine plan: a paid subscription, an organization seat, or an active Premium trial. The Individual plan is $5.99 per month or $59.99 per year.
None of that involves a webhook URL. ConnectMachine ships as a native Zapier app, so connecting it is a sign-in, and the Zapier documentation carries the prerequisites, the OAuth scopes, and the full field reference. Everything past this point is about the Salesforce end of the Zap.
## Step by step: ConnectMachine to Salesforce
### 1. Read your admin's requirements first
Open the Lead object in Setup and write down every required field and every validation rule that fires on save. Ten minutes here saves an hour of reading Zapier error messages later, and it is the step everyone skips.
### 2. Scan one card, then open the template
Zapier builds the mapping against a real record pulled from your account, so scan someone before you start. Then use the Create Salesforce leads from new ConnectMachine contacts template rather than a blank Zap: it arrives with the New Contact trigger and the Salesforce lead action already wired.
### 3. Connect both accounts, and check which org
ConnectMachine signs you in with Google or an emailed code, never a password. Salesforce then asks which org to authorize, and this is where afternoons disappear: connect a sandbox, wonder why production is empty. The consent screen and the scopes behind it are documented in the Zapier docs.
### 4. Fill everything Salesforce insists on
Work through the list from step one. Last name and company are the floor on a standard lead; your org has almost certainly added lead source, a region, an owner assignment rule, or something a validation rule checks. Map them all before you test.
### 5. Send one lead, open it, then publish
Look at the record in Salesforce the way the rep who inherits it would. If the company is right, the source is reportable, and the notes are somewhere findable, publish the Zap.
## Map and test the lead fields
The trigger hands Zapier a structured contact rather than a blob of text, which is what keeps the mapping short. The full field list is in the docs. What matters here is that Salesforce is stricter than any other destination in the set, so the mapping is less about coverage and more about satisfying the object.
- Map first name and last name separately. ConnectMachine already splits them, so do not push a single full name into the last name field and lose the split.
- Give the company field a fallback. A card from a freelancer often has no company on it, and an empty company is the most common reason a lead refuses to save.
- Set lead source to a static value you can report on. Something like Event scan tells you months later where the pipeline actually came from, and costs nothing to add now.
- Send your ConnectMachine notes and the where you met value into the lead description or a custom field. That context is the difference between a name and a conversation you can reopen.
- Leave optional Salesforce fields unmapped rather than filling them with placeholder text you will have to clean up later.
Test with a real scanned contact rather than Zapier's generic sample. Salesforce enforces field length limits that a sample never reaches, so the failure you are hunting is the card belonging to a Senior Director of Strategic Partnerships and Business Development, whose job title is longer than the field holding it.
## Prevent duplicate leads
Read this part before you turn the Zap on. ConnectMachine's Zapier app publishes no search action, so the usual find-or-create pattern is not available and the Zap writes without checking. Unlike HubSpot, Salesforce has no deduplication you can assume is switched on, which makes this the riskier of the two integrations to leave unguarded.
Salesforce can match incoming leads against records you already hold, but whether it warns, blocks, or quietly allows the write is entirely down to how your admin configured the matching and duplicate rules. Do not guess. Open the rules, read what they do on create, and only then decide how much of the guarding your Zap has to handle itself.
- Do not treat the Zap as a cleanup step. Merging duplicate leads happens in Salesforce, by hand or through your own duplicate rules.
- Do not assume duplicate rules are switched on, or that they block rather than warn.
- Do not run it without a filter if you also import lists into ConnectMachine, or one import becomes hundreds of Salesforce writes.
- Do not assume a lead edited in Salesforce flows back. It does not.
The practical guard is a Zapier filter between the trigger and the action: continue only when the contact has an email address, and, if you tag contacts in ConnectMachine, only when the tag says this person belongs in the pipeline. Both take a minute, and on an org where sales ops audits duplicate leads quarterly they are what keeps you out of that meeting.
## What triggers the Zap
There is no separate scan trigger. New Contact fires on any contact created in ConnectMachine, so a spreadsheet you imported on Monday would open leads in your pipeline on Monday. Filtering is what keeps the trigger honest about which cards deserve a lead record.
The docs cover the full set: three triggers, two actions, and the source value that lets you stop two Zaps from feeding each other.
## Troubleshooting the Salesforce side
### Salesforce rejects the test
Usually a required field with nothing mapped to it, or a validation rule doing its job. The error names what failed, so map the field or ask your admin which rule is firing, then re-run.
### The leads land in the wrong place
Check which org you authorized, and whether an assignment rule is reassigning the owner after the write. Both look like the Zap misbehaving and neither is.
### The lead saves but the description is truncated
A Salesforce field length limit, not a mapping error. Long notes need a long text area field rather than the standard description, which is a change your admin makes once.
### Zapier says the Salesforce connection needs an upgrade
Zapier prices some CRM connections above its free tier. This is a Zapier plan question rather than anything on the ConnectMachine or Salesforce side.
Connection refusals, missing sample data, a 410 Gone on the trigger, and the rest of the ConnectMachine-side failures are covered in the Zapier troubleshooting section.
## Other ready-to-use workflows
Salesforce is one of several published templates. The same scan can also become a HubSpot contact, a Slack message, a Gmail follow-up, or a Close lead. Posting the new lead into a Slack channel alongside the Salesforce write is the pairing most sales teams end up with: the pipeline gets the record, the floor gets the heads-up while the person is still in the room.
If HubSpot is your CRM instead, the HubSpot business card scanner guide covers that route, and a HubSpot contact asks for far less than a Salesforce lead does. The Zapier integration page lists the current templates with a one-click open for each, including the ones that write into ConnectMachine rather than out of it.
[See every ConnectMachine Zap](/integrations/zapier/)
## Capturing inside Salesforce vs ConnectMachine plus Zapier
### Where capturing inside Salesforce wins
One system, one login, nothing to maintain between two vendors. If Salesforce is the single source of truth, every person you meet is a sales record, and your whole team lives in the CRM anyway, the shortest path is the one that never leaves it.
### Where ConnectMachine plus Zapier wins
The capture is separate from the CRM. People you are not ready to make leads still get saved with notes, the same scan can reach several tools at once, and the network you build stays yours when you change employers or your company changes CRM. Reps move. Orgs get migrated. The cards should survive both.
A reasonable test: if the answer to what happens to a card that is not a lead yet is that it gets thrown away, capture inside Salesforce. If the answer is that you want to keep the person, keep them in a contact manager and let the Zap decide what Salesforce sees. For a team working the floor at events, the sales rep workflow covers what capture looks like before any of it reaches the pipeline.
## Salesforce lead capture for a whole event, not one card
One card is a setup problem. Sixty cards over two days is a different problem, and it is the one that actually costs pipeline. The Zap above handles both, but the volume case needs two decisions made before the event rather than during it.
### Decide the tag before you go
Agree one tag in ConnectMachine that means this person belongs in the pipeline, and have the whole team use it. The Zapier filter reads that tag, so the difference between a clean event import and four hundred unqualified leads is a word everyone agreed on beforehand.
### Set lead source to the event, not to the channel
A static lead source of Event scan tells you the channel. A source naming the actual event tells you which booth paid for itself. Change the static value in the Zap the morning the event opens and change it back afterwards, and your pipeline reporting answers a question your finance team is already asking.
Capture speed matters more than completeness on the floor. Scan, add one line about what you discussed, move on; the Zap fills the CRM while you are still talking to the next person. What that looks like in practice for a team working a stand is covered in capturing business cards at a conference and in event lead capture.
## Frequently asked questions
### What is the best business card scanner for Salesforce?
It depends on the volume and the destination. A CSV import clears a one-off backlog, an AppExchange scanner suits teams who never leave the CRM, and a capture app plus Zapier fits a steady drip of cards that also need to reach Slack, email, or a network you keep yourself.
### How do I get business card scans into Salesforce?
Scan the card in ConnectMachine, then run the public Zapier template that creates a Salesforce lead from each new ConnectMachine contact. Connect both accounts, map the fields Salesforce requires, test one record, and turn the Zap on.
### Does the Zap create a Salesforce lead or a contact?
The published template creates a lead, which suits cards from people your team still has to qualify. If the person is a known relationship rather than a prospect, swap the Salesforce step for Create Contact or filter which cards take the lead path.
### Why does Salesforce reject the lead my Zap creates?
Almost always a required field with nothing mapped to it or a validation rule firing on save. A standard lead needs a last name and a company at minimum, and most orgs add more. The Zapier error names what failed.
### Will the Zap create duplicate Salesforce leads?
It can. There is no ConnectMachine search step, so the Zap cannot check for an existing record before it writes. Salesforce duplicate and matching rules may catch it, but whether they warn, block, or allow depends on how your admin configured them. A filter requiring an email is the practical guard.
### Is the ConnectMachine to Salesforce Zap a two-way sync?
No. The template creates a Salesforce lead from a new ConnectMachine contact. Changes made in Salesforce afterwards do not flow back unless you build a second Zap using the Create Contact or Update Contact action.
### Will the Zap also send contacts I did not scan?
No. New Contact fires on every contact created in ConnectMachine, imports and manual entries included. Without a filter, one imported list becomes a few hundred leads your sales ops team did not ask for.
### What does the Salesforce Zap cost?
Zapier access needs an eligible ConnectMachine paid plan, organization license, or active Premium trial; the Individual plan is $5.99 per month or $59.99 per year. Check your Zapier plan separately, since Zapier prices some CRM connections above its free tier.
## Get the card into Salesforce before the drawer gets it.
Scan cards with ConnectMachine and let one Zap create the Salesforce lead. Open the public template, connect both accounts, and your next scan arrives in the pipeline with your notes attached.
[Get ConnectMachine](/download-app)