Pipedrive Digital Business Cards: CRM Integration Guide

Pipedrive is built around one idea: sales happen through activity, and activity should be measured. Every call, email, tap, and touchpoint should produce a record in the pipeline. This philosophy maps naturally onto digital business card workflows — because every card scan is an activity, and every activity should drive a next step.

This guide covers end-to-end Pipedrive integration with digital business cards: platform selection, connection setup, field mapping, activity automation, pipeline configuration, Wallet pass workflows, and the reporting that tells you whether the channel is actually producing.

Why Pipedrive Suits This Workflow

Pipedrive's strengths align well with event-based networking:

• Pipeline visualization: Deal stages are clear, visual, and easy to move prospects through
• Activity-based selling: The system prompts reps to take the next action on every contact
• Affordable for teams: Lower per-user cost than Salesforce; simpler setup than HubSpot
• Workflow Automation: Built-in automation on Growth plan and above — essential for card-triggered follow-up sequences

The integration pattern: card scan → Pipedrive Person and Lead created → Activity scheduled → Rep follows up → Deal progresses. No manual data entry, no forgotten contacts.

Current Pipedrive Pricing (2025–2026)

Pipedrive restructured its plans in 2025 from five tiers to four:

Plan	Annual billing	Monthly billing
Lite	$14/user/mo	$24/user/mo
Growth	$39/user/mo	$49/user/mo
Premium	$49/user/mo	$79/user/mo
Ultimate	$79/user/mo	$99/user/mo

The Growth plan includes Workflow Automation — essential for the follow-up sequences described in this guide. Lite does not include Workflow Automation, which significantly limits what you can automate from a card scan event.

Platforms with Native Pipedrive Integration

Not every digital business card platform connects natively to Pipedrive. Confirmed native integrations (2025–2026):

Platform	Pipedrive integration	Plans that include it	Approx. price
HiHello	Native	Business	$6/user/mo (annual)
Mobilo	Native	Plus and Team	$4/user/mo (annual)
Popl	Native	Teams	$4/user/mo (annual)
Blinq	Via Zapier	Premium and Business	$4.99–$6.99/user/mo (annual)

HiHello and Mobilo tend to have the most polished native integrations, with dedicated field mapping UIs and event-tagging support. Blinq's Zapier path is functional but requires manually configuring the zap.

Step 1: Connect Your Platform to Pipedrive

In your digital card platform's dashboard, navigate to Integrations → CRM → Pipedrive.

OAuth (recommended for individual users): Sign into Pipedrive, approve the access scope. Fast and revocable from Pipedrive's connected apps settings.

API Token (recommended for team accounts): Found in Pipedrive under Settings → Personal Preferences → API. Useful when connecting via a service account rather than a personal login.

After connecting, send a test scan through the system to confirm data flows correctly before rolling out to your team.

Step 2: Choose What Gets Created

Pipedrive has three main object types for managing prospects:

• Person: A contact record — always create this
• Lead: An early-stage opportunity — create when form data is submitted (intent implied)
• Deal: An active pipeline opportunity — create when higher-intent signals are present (meeting booked, budget expressed)

Recommended default configuration:
- Card tap + form submitted → Person + Lead
- Meeting booked from profile → Person + Lead + Deal (promoted automatically)
- Card tap only, no form → Person only (rep reviews manually)

This prevents your pipeline from flooding with unqualified contacts while ensuring anyone who expressed intent gets full pipeline treatment.

Step 3: Field Mapping

Map profile and form data to Pipedrive fields:

Person fields:
- Name → Person Name
- Email → Person Email (primary)
- Phone → Person Phone
- Company → Linked Organization (Pipedrive creates if absent)
- Title → Person Title (Job Position)

Lead/Deal fields:
- Title: [Person Name] – [Event Name]
- Pipeline stage: First/earliest stage (e.g., "Initial Contact")
- Value: Leave blank or set a default estimate
- Owner: Card owner's Pipedrive user

Custom fields worth adding:
- Lead Source: "Digital Business Card"
- Event Name: Conference, trade show, meeting
- Trigger Type: "NFC tap" / "QR scan" / "Link click" (enables channel-level analytics)
- Card Owner: Useful for multi-rep reporting

Step 4: Activity Setup

Pipedrive's value is in activities — the system that tells reps what to do next. Configure automatic activity creation on card scan:

On Person + Lead creation:
- Activity type: Email
- Subject: "Follow up with [Name] from [Event]"
- Due date: 24 hours after scan
- Assigned to: Card owner

Three-touch sequence via Workflow Automation:
- Day 1: Personalized follow-up email
- Day 3: Relevant case study or content share
- Day 7: Discovery call request

The automation ensures consistent follow-up without relying on individual rep discipline after a busy event day.

Step 5: Owner Assignment

Card-owner-based (standard): Each rep's scans create records owned by that rep. Set in team/user settings within your card platform. Most teams use this — it creates clear accountability.

Round-robin: For shared "Sales Team" cards or event booth cards, distribute leads evenly across team members.

Manager review queue: For high-volume scenarios, create records assigned to a team lead who routes before activating follow-up.

Step 6: Workflow Automation (Growth Plan+)

Pipedrive's Workflow Automation handles downstream actions automatically:

Welcome email trigger:
- When: Lead created with Source = "Digital Business Card"
- Action: Send email template "Thanks for connecting at [Event]"

Activity on lead creation:
- When: Lead created
- Action: Create Activity "Send follow-up email" due in 24 hours

Stage progression:
- When: Person submits meeting booking form
- Action: Convert Lead to Deal, move to "Discovery" stage

Rep notification:
- When: Lead assigned to rep
- Action: Notification in Pipedrive Inbox + optional email alert

These automations run without rep intervention, ensuring every scan produces a concrete next step.

Step 7: Apple Wallet in the Pipeline

Apple Wallet passes are entry points into your Pipedrive pipeline, not a separate channel.

The flow: recipient taps your NFC card or scans your QR → lands on profile → adds to Apple Wallet via PassKit → later returns to your profile via the Wallet link → submits a form → Pipedrive record created.

Apple Wallet passes include a link back to your profile. When a recipient is ready to reach out — possibly weeks after the initial exchange — the pass in their Wallet is the navigation mechanism back to your lead form and booking link.

Advanced configuration:
- Tag Apple Wallet-sourced submissions separately ("Source: Apple Wallet return") to understand re-engagement lag
- Set pass location alerts (up to 10 GPS coordinates) so your card resurfaces on the recipient's lock screen near your office or regular event venues
- Track pass-add events as Pipedrive activities if your platform supports webhooks on Wallet installs

Step 8: Google Wallet in the Pipeline

Google Wallet passes via the Google Wallet API work identically. Android recipients save your pass, carry it passively, and return to your profile when ready.

Google Wallet's Quick Access feature means your card can appear on the recipient's lock screen by swiping up — no unlock required. This passive resurfacing drives re-engagement that paper cards can't replicate.

Tracking tip: differentiate "Google Wallet return" from "Apple Wallet return" via custom form fields if you want platform-level attribution in Pipedrive.

Step 9: Pipeline Structure for Card-Generated Leads

Recommended stages for a digital card lead pipeline:

1. Initial Contact — card scanned, Person created
2. Engaged — form submitted, Lead confirmed
3. Discovery — meeting booked
4. Proposal — formal proposal sent
5. Negotiation
6. Closed Won / Closed Lost

Card scans generate leads at stage 1 or 2. Form submissions advance to stage 2. Meeting bookings advance to stage 3. The pipeline makes each lead's journey visible and auditable.

Step 10: Reporting in Pipedrive Insights

Build these dashboards to measure the card channel:

Channel attribution:
- Filter: Leads/Deals with Source = "Digital Business Card"
- Metrics: Count, total value, conversion rate to Deal, average days to close

Event ROI:
- Filter: Event field = "[Specific event name]"
- Metrics: Pipeline value, Deal count, win rate

Rep performance:
- Group by: Card/Lead owner
- Compare conversion rates, follow-up speed, win rates

Review monthly. The visibility surfaces which events, which reps, and which follow-up sequences perform — and which don't.

Handling Duplicates

Pipedrive deduplicates by email by default. Edge cases to configure for:

• Same person scans multiple cards at one event → log an Activity on the existing Person instead of creating a duplicate
• Existing customer scans your card → create a new Deal on their record (not a new Lead)
• Same email submits the form twice → update existing record with new event tag, don't duplicate

Most card platforms expose deduplication logic in their Pipedrive integration settings.

Real-World Scenario: 15-Rep B2B Sales Team

A 15-rep team using HiHello with Pipedrive Growth:

Metric	Number
Events per month	4
Average scans per event	80
Total monthly scans	320
Form submission rate	25% → 80 Leads
Automated follow-up sent	80 (100%)
Meetings booked	28% of Leads → ~22
Deals to Proposal	45% → ~10
Closed Won (30%, avg $30k)	~3 deals/month
Monthly revenue from card channel	~$90,000

Annual card platform cost: 15 users × $6/month (HiHello Business) = $1,080/year

Pipedrive Growth incremental cost: 15 × $39/mo = $7,020/year (likely already in use)

Card channel ROI: well above 50x on the platform cost alone.

Common Integration Issues

Leads not appearing in Pipedrive: Check OAuth or API token status — tokens occasionally expire. Re-authenticate.

Duplicate Persons created: Configure email-based deduplication in your card platform's integration settings.

Activities not auto-created: Check Workflow Automation trigger conditions — they need to exactly match the data structure the integration sends.

Wrong owner assigned: Verify each rep's card is mapped to their Pipedrive user in team settings.

A Note for Solo Professionals

If you're a solo practitioner or a small team without a dedicated sales process, a full Pipedrive integration may be more overhead than you actually use.

BizBuzz Cards includes a built-in contact-save CRM and AI-powered semantic search across your saved network — you can find that product manager you met at the October fintech meetup by searching a description of the conversation, not just a name. For solo networkers, this built-in layer may be the entire system you need, with no CRM configuration required. Upgrade to Pipedrive when your team size and volume justify the investment.

When Pipedrive Is the Right Choice

Pipedrive beats alternatives when:
- Team size is 5–100 reps
- Sales process is relationship-driven and activity-tracked
- Budget is a constraint relative to Salesforce
- You want fast onboarding without heavy customization or data model complexity

Consider HubSpot instead if marketing automation depth is a priority. Consider Salesforce instead for complex enterprise requirements, territory management, or teams above ~200 reps with advanced compliance needs.

Final Checklist

1. Choose a platform with native Pipedrive integration (HiHello, Mobilo, Popl)
2. Connect via OAuth or API token; verify with a test scan
3. Configure Person + Lead creation on form submission
4. Map fields including lead source, event name, and trigger type
5. Set up Workflow Automation for follow-up sequences (Growth plan required)
6. Configure Apple Wallet and Google Wallet as re-engagement channels
7. Build pipeline stages reflecting your card-to-close journey
8. Create Insights dashboards for monthly channel review
9. Train reps on consistent follow-up habits on top of the automation baseline

The setup takes an afternoon. The compounding payoff runs across every event you attend afterward.

Sources

• Pipedrive Pricing
• Pipedrive Workflow Automation
• HiHello Pricing
• Mobilo Pricing
• Popl Pricing
• Blinq Pricing
• Google Wallet API Documentation
• Apple PassKit Documentation
• PassKit: GPS Location Notifications for Passes