Skip to main content

Home

Clay Announcements
Discuss Anything
GTM Career Advice
Introduce Yourself
Member Spotlight
Share Content and Events
Share Full-time Jobs
Share Part Time Jobs
Share Tables, Tools, and Workflows

Community Guidelines

Hire GTME Talent
Explore Events

Powered by Tightknit

Discuss Anything

Discuss Anything

Managing Multiple HubSpot and Salesforce Connections in Clay: Best Practices and Safe Cleanup Steps

·Apr 27, 2026 06:20 PM·

👋 Hey I'm Teresa López, the new Marketing Ops lead on the RevOps side at Hearth. Nice to e-meet you all! I'm running an audit on our Clay workspace and wanted to flag something for your input: We currently have 3 HubSpot connections and 3 Salesforce connections authorized in Clay. Is it true that having multiple connections to the same system creates real risk — writes (enrichments, pushes, updates) could hit the wrong account or land in a sandbox instead of production, and it makes it hard to govern which credentials/permissions are actually in use? Could you help me with the following:

1.
What can I do to confirm which HubSpot connection and which Salesforce connection are the canonical / production ones we should standardize on.
2.
If its required to remove 2 out of 3 connections, how can I do that safely?

Goal is just one source of truth per system as a best practice (if needed). Appreciate the help 🙏

4 comments

· Sorted by Oldest

Abdul S.
·
·
Hey Tere! yeah multiple connections are a governance nightmare. to find your production ones: check which connections have active workflows in clay, then test each with a quick table query to see which pulls live data. document that one as canonical, then safely remove the others. clay will flag if workflows are attached so you won't break anything. happy to help if you hit snags.
Tere L.
·
(edited)·
Thank you Abdul, got it, so if I remove a connection from someone you are saying clay will flag if workflows are attached so you I don't break anything ?
Abdul S.
·
·
yeah clay flags which workflows are attached before you delete. migrate those to your canonical connection first, then delete safe
Salman T.
·
·
Hey Teresa — been down this road before, happy to help. Don't delete anything yet. The risk isn't the deletion itself, it's deleting while something is still pointing to that connection. Clay won't warn you, it'll just silently break. Here's the order that actually works: Go to Settings → Connections, open HubSpot, test each one. The account name/email will show — match that against your actual production HubSpot portal. Do the same for Salesforce. You're looking for the ones tied to your live orgs, not a sandbox or an old employee's credentials. Once you've confirmed each one, set them as Default immediately. Don't skip this step. Now before you delete the others — go through your Clay tables and check every enrichment column and workflow action that pushes to HubSpot or Salesforce. If any of them have a specific connection selected (not default), switch those over manually to the ones you're keeping. After that's done, deleting the extras is completely safe. The whole thing takes maybe 20-30 mins depending on how many tables you have. Lmk if you want me to walk through any part of it.