Claude workflow
Find duplicate contacts and companies with Claude
Spot the records that are probably the same, see the evidence and propose the merges.
What does this workflow do?
Claude reads companies or contacts in pages, finds pairs with the same domain or email, near-identical names or the same phone, and shows each pair with which record should survive. For the pairs you confirm it files a merge proposal, which waits for approval on the Feed in Lumenbase. It never merges on its own.
The prompt
Copy it into a chat with Lumenbase turned on. Fields in square brackets are yours to fill in.
Use the Lumenbase connector. 1. Read companies with fetch_contacts or fetch_companies, in pages of 100. 2. Find pairs that are probably the same: same domain or email, near-identical names, same phone. 3. Show me each pair with the evidence and which record should survive. 4. For the pairs I confirm, call propose_merge. It creates a merge proposal for review in Lumenbase; it does not merge on its own.
Run it as /clean_duplicates in Claude.
Fields you can fill in
entity(optional): "contacts" or "companies". Default companies.
Tools it calls
In the order the prompt uses them.
- Propose duplicate merge · Write
Propose merging a likely duplicate record into another (same entity type).
What to check before you approve
- The evidence really points to one company or person.
- The surviving record is the one with the most history.
- Two different people at the same company are not paired.
Common questions
Sources and scope
The prompt and its tool list come from the Lumenbase MCP workflow catalog, the same list the connector serves.
Claude is a trademark of Anthropic. ChatGPT is a trademark of OpenAI. Cursor is a trademark of Anysphere. Lumenbase is not affiliated with, sponsored by or endorsed by these companies.