Menu

Bad data costs real money. Here is the HubSpot to Supabase workflow that fixed it.
📰

Bad data costs real money. Here is the HubSpot to Supabase workflow that fixed it.

DEV Community: postgres·Adan Potyondy·11 days ago
#q4GCeYJQ
#devtopostgresql#devto#dev#hubspot#customer
Reading 0:00
15s threshold

In September I worked with a customer on a data quality problem and recorded a short demo of the general case. Contacts come out of HubSpot, get cleaned and deduplicated, and only the rows that pass land in Supabase.

The interactive demo is on the original post. Here is a separate 6-minute live build of the same flow; it matches duplicates with fuzzy (Jaro-Winkler) matching rather than the exact email match described below.

The problem the customer brought us

Their sales team lives in HubSpot. Their product and reporting live on a Supabase database. A nightly job copied contacts from one to the other, and it copied everything: the same person three times under three spellings of their email, trailing spaces in names, companies typed in four different ways, and records with no usable email at all.

None of that looks dramatic in a CRM. It looks dramatic in the results.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.