LEAD GENERATION

Badge-Scan CSV Importer with HubSpot Dedupe

Watches a Drive folder for raw badge-scan CSV exports, normalizes the rows, and upserts each lead into HubSpot.

CategoryLead Generation
Enginesim
Difficultybeginner
Triggerevent
Steps6
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNew badge-scan CSV in Drive folderGoogle DriveGoogle Drive
  • ActionParse and normalize scan rows
  • ActionLook up contact in HubSpot by emailHubSpotHubSpot
  • LogicBranch: existing contact vs. new lead
  • ActionUpsert contact with event source propertyHubSpotHubSpot
  • OutputPost import summary to SlackSlack

What it does

Turns the messy CSV your booth scanner spits out into clean, deduplicated HubSpot contacts. Email, name, company, and job title are normalized, then matched against existing CRM records before anything is written, so a returning attendee updates their record instead of spawning a duplicate.

When to use it

Run it the morning after each event day when your lead-capture vendor drops a fresh export. Best for teams who live in HubSpot and want every scanned badge in the funnel within minutes — without an SDR hand-cleaning spreadsheets.

How it works

  1. 1A new badge-scan CSV lands in the watched Google Drive folder and fires the trigger.
  2. 2The file is parsed and each row normalized — lowercased email, trimmed company, mapped title.
  3. 3For each lead, HubSpot is queried by email to check for an existing contact.
  4. 4A branch decides: update the matched contact, or create a net-new one tagged with the event source.
  5. 5Every contact gets a "Conference – [event]" lifecycle property and a Slack summary posts the import count.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect Google DriveDocs, sheets, slides, files.
  2. 2
    Connect HubSpotCRM, deals, marketing, support.
  3. 3
    Connect SlackChannels, DMs, threads, mentions.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.