CRM Connection Detail
Manage a CRM connection, read its status and any connection issue in plain words, test sync, and recheck resolved provider setup warnings safely.
Overview
Manage one CRM connection: connect, choose a safe start, control sync types, set a record owner, test the connection, and watch sync health. VanillaSoft connects through an Incoming Web Lead instead of a sign-in. SalesHive only adds and updates CRM records. It never deletes them.
How to use this page
Connect the CRM
Use Connect or Reconnect on the status card. Its heading tells you where things stand: Not syncing means the app is disconnected and SalesHive is sending nothing until you reconnect; Sync is retrying means the CRM refused the last 3 or more sync attempts, and SalesHive retries about every 5 minutes; Connection needs attention means the connection is in an error state. Your existing CRM data is safe in each case. The setup guide tracks connection, starting point, field mapping, and a test contact. VanillaSoft has no Connect sign-in button; set up its web lead as described below.
Read a connection issue
When the connection has a problem, a line under the status card names it in plain words, for example Reconnect needed with what it means and how to fix it. A disconnected app always reads Reconnect needed. Open Technical details to see the CRM's own error text, for example to share with your CRM admin. Setup warnings, such as a missing Salesforce field, stay until they are fixed. A one-off record error that later sync runs recovered from no longer shows here; check Recent sync activity for record-level failures.
Connect VanillaSoft with a web lead
Follow the numbered steps in Set up a VanillaSoft web lead: in VanillaSoft, add an Incoming Web Lead named SalesHive, turn on Create New Contacts (and Update Existing Contacts matching on Email), map each field you want using the Web Form Field names listed on the page, tick Active and save. Copy the full posting URL with its verification key, paste it into Posting URL, tick the box if the web lead updates existing contacts, and click Connect VanillaSoft. SalesHive checks the web lead before saving.
Choose a safe starting point
After connecting, Start fresh is recommended when you are unsure. It syncs only new activity. Import existing contacts can push up to the displayed number of SalesHive contacts, create or update CRM records, and trigger CRM workflows or notifications, so it opens a confirmation before it starts.
Re-import existing contacts deliberately
After initial setup, select Resync contacts when you need to push historical contacts again. Review the confirmation before continuing because the same bulk changes and CRM-side workflows can occur. SalesHive cannot automatically undo an import.
Choose what syncs and prove the connection
Use the Contacts, Emails, Calls, and Meetings toggles to control new activity. A self-serve workspace has no dialer, so it does not see the Calls toggle. Set an optional record owner for new records where available (VanillaSoft has no Record owner section), then use Test connection to send a labeled test contact through the real sync path. For VanillaSoft, look for SalesHive Sync Test in your VanillaSoft project.
Resolve a Salesforce External ID warning
If Salesforce cannot create its Lead dedupe field automatically, sync continues with email-based matching and the page shows setup guidance. Ask a Salesforce admin to add a Text(255) Lead field named SalesHive_External_Id__c with External ID and Unique enabled. Revisit the page or select Re-run setup to check Salesforce again. The resolved setup warning clears only after the field is detected.
Review sync health
Use Last 24 hours and Recent sync activity to review outcomes. While the sync is retrying and no records failed, Last 24 hours says the CRM is not accepting the connection right now instead of No action needed; fix the connection issue above rather than retrying records. The Details column includes failure reasons and warnings on successful syncs. A successful HubSpot sync with a Possible duplicate warning still completed; review the named records before merging anyone. For a failed identity conflict, correct the cause before selecting Retry failed records. If a write could not be confirmed, check the record in HubSpot before retrying. For a HubSpot call to a prospect with no email, Details names the contact or company it was logged on, or starts with Call skipped. and says why no single record matched. On a Salesforce connection that sends people as Leads, a successful sync can carry a note that the lead was converted and activity is logged on the Contact it became; no action is needed. A failure whose Details start with Converted lead needs review means that Contact could not be found, and nothing was sent.
What the buttons do
- Start fresh (recommended)
- Skips historical import and begins syncing new activity only. You can choose a historical import later.
- Import N
- Opens a confirmation before the one-time historical import of existing contacts.
- Re-run setup
- Reopens the setup guide. For Salesforce, it also checks whether the required Lead external ID field is now available and reports the result.
- Resync contacts
- Opens a confirmation before re-importing existing contacts.
- Test connection
- Pushes one labeled test record through the real CRM sync path.
- Retry failed records
- Queues failed records for the next scheduled sync after the cause is fixed.
- Posting URL / Connect VanillaSoft
- VanillaSoft only. Paste the web lead's full posting URL, then connect. SalesHive checks that VanillaSoft recognizes the web lead before saving it. Shows Reconnect VanillaSoft when a past connection exists.
- VanillaSoft updates existing contacts, matching on Email
- VanillaSoft only. On: SalesHive keeps each contact current and records calls, emails and meetings on it. Off: each contact is sent once and later changes and activity are skipped, so nothing is duplicated. Turn on Update Existing Contacts in the web lead first.
- Web Form Field names SalesHive sends
- VanillaSoft only. Lists each Web Form Field name SalesHive can send and what it holds, to copy into your web lead's field mappings. Open by default before you connect.
- Technical details
- Under a connection issue, expands the exact error the CRM returned. The plain-language explanation above it says what to do.
Common questions
Why does importing existing contacts need confirmation?
Which option should I choose first?
Does SalesHive delete CRM records?
Will Salesforce create duplicate Leads without the custom External ID field?
How do I clear a resolved Salesforce setup warning?
What happens after my team converts a Salesforce lead?
What does Converted lead needs review mean in Details?
Why is a Salesforce call's numeric field blank?
Will VanillaSoft create duplicate contacts?
Where do VanillaSoft calls, emails and meetings go?
Why did connecting show OAuth flow failed: invalid_state?
How does HubSpot match an existing contact?
How are HubSpot calls logged for a prospect with no email?
Does Possible duplicate mean the sync failed?
Will SalesHive create a second HubSpot meeting when my team already booked it in HubSpot?
Why does Record owner ask me to disconnect and reconnect?
What does Sync is retrying mean?
Why does my HubSpot connection say Not syncing?
Are the sample prospects from our SalesHive demo sent to this CRM?
Get an answer from a real person
These guides cover the everyday questions. For anything they miss, we are easy to reach.
Contact support
Tell us what you are trying to do and where you got stuck. A real person on the SalesHive team replies, not a ticket bot.
Send us a messageSign in to the platform
Already a client? These same guides are built into the app: open the help panel on any page for the walkthrough that matches the screen you are on.
Open the platformLet’s talk about your sales goals
Talk with our team about our services, pricing and how we can help your team grow.
Category: Platform · Settings