LEAD GENERATION

Dedupe event attendee lists in a Coda tracker with a reviewable merge log

Pulls newly imported event attendees from a Coda table, finds fuzzy duplicates against rows already in the tracker.

CategoryLead Generation
Enginesim
Difficultyintermediate
Triggerschedule
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerDaily schedule fires
  • ActionRead attendee rows from Coda trackerCodaCoda
  • LogicScore fuzzy name + domain duplicate pairs
  • LogicBranch: auto-merge vs flag for review
  • ActionMerge confident duplicates in CodaCodaCoda
  • OutputAppend merges and flags to Coda merge logCodaCoda

What it does

When booth staff and a list-rental vendor both feed attendees into the same Coda tracker, you get near-duplicates: "Jon Smith / Acme" and "Jonathan Smith / Acme Inc." This workflow finds those pairs, merges them onto a single canonical row, and records what it merged so a human can audit or reverse it.

When to use it

Use it when your event pipeline lives in Coda and several sources write to one attendee table. Run it on a schedule so the tracker stays clean without anyone hand-merging rows.

How it works

  1. 1A daily schedule kicks off the run.
  2. 2The flow reads all attendee rows from the Coda table, flagging the ones added since the last run.
  3. 3It scores fuzzy matches on name plus normalized company domain to find likely duplicates.
  4. 4A branch separates confident matches (auto-merge) from ambiguous pairs (flag only).
  5. 5Confident pairs are merged into the canonical row in Coda, keeping the earliest first-touch date.
  6. 6Every merge and every flagged pair is appended to a Coda merge-log table for review.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect CodaDocs, packs, automations.
  2. 2
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  3. 3
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  4. 4
    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.