Help CenterPlatform · Settings

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.

Updated Nov 20, 2026 8 steps 19 questions answered
On this page

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

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

  6. 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.

  7. 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.

  8. 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?
A bulk import can create or update CRM records and can trigger CRM workflows, assignments, or notifications. SalesHive cannot automatically undo it.
Which option should I choose first?
If you are unsure, choose Start fresh. It only syncs new activity, and you can import historical contacts later.
Does SalesHive delete CRM records?
No. The connection is one-way from SalesHive and only adds or updates records. Disconnecting stops future pushes and leaves existing CRM records in place.
Will Salesforce create duplicate Leads without the custom External ID field?
SalesHive falls back to email-based matching when the field is unavailable, so sync can continue. Adding SalesHive_External_Id__c as a unique External ID gives each mirrored SalesHive contact a stronger stable match.
How do I clear a resolved Salesforce setup warning?
After a Salesforce admin adds or repairs the required Lead field, revisit the connection page or select Re-run setup. SalesHive checks for the field, clears only the matching resolved setup warning, and preserves newer sync or authorization errors. If the field is still unavailable, the warning remains.
What happens after my team converts a Salesforce lead?
This applies to a Salesforce connection that sends people as Leads (on Field Mapping, How records land in your CRM is set to Leads). Once your team converts a lead, SalesHive stops writing to it: the converted lead is never updated and never gets a new task or event. Emails, calls and meetings are logged on the Contact the lead became instead. That Contact stays yours: SalesHive does not change its fields, owner or status. If the person also has an open lead, the open lead is used and updated as before. SalesHive does not create a new lead for someone who exists only as a converted lead. Salesforce connections set to Contacts & Accounts, and other CRMs, work as they did. A successful sync after the conversion can show a note in Details, under Recent sync activity, saying the lead was converted and activity is logged on the Contact it became. No action is needed.
What does Converted lead needs review mean in Details?
The person was a Salesforce lead your team converted, and SalesHive could not find one Contact to log their activity on. Details says which case applies: the Contact the lead became is no longer in Salesforce (deleted or merged), or leads for this person were converted to different Contacts. It names the Salesforce record IDs involved so your Salesforce admin can look them up. Nothing was sent, because SalesHive never writes to a converted lead and never guesses where a person belongs. If this person should still get activity in Salesforce, create a new open lead with their email, then select Retry failed records. If they should not, no action is needed. On the Integrations page, Sync Health lists these under Not yet in your CRM as Converted lead with no contact to follow.
Why is a Salesforce call's numeric field blank?
SalesHive converts valid numeric values before sending a call activity to Salesforce. A nonnumeric value is omitted, and a whole-number field such as call duration also rejects decimals. Open Field Mapping on Integrations, expand Advanced · Activity & call-outcome mapping, and check the source and destination fields. Correct the mapping or source value as needed; a successful call sync does not mean every optional field was included.
Will VanillaSoft create duplicate contacts?
Not when Update Existing Contacts is on in your web lead, matching on Email, and the matching box is ticked here: every post updates the same contact. While it is off, SalesHive sends each contact once and skips later changes.
Where do VanillaSoft calls, emails and meetings go?
VanillaSoft cannot receive activity records, so SalesHive fills fields on the contact instead: last call result, date and notes, last email date and subject, and meeting date and notes. Map the ones you want in your web lead. SalesHive cannot read data back from VanillaSoft, and a field fills only if your web lead maps its exact Web Form Field name.
Why did connecting show OAuth flow failed: invalid_state?
A Salesforce, HubSpot, Pipedrive or Zoho connection must finish in the same browser, signed in as the same SalesHive user, with the same client selected as when you started it. If you signed in as someone else, switched clients, or sent the provider sign-in link to another person to approve, the connection stops and nothing is saved. Select Connect again from the client you want to connect, and complete the provider sign-in yourself.
How does HubSpot match an existing contact?
SalesHive checks its saved HubSpot link, then the SalesHive ID stored in HubSpot, then a HubSpot Record ID saved on the contact (for example from a CSV, Zapier or API import), then the email being sent. A saved Record ID is used only when that HubSpot contact is not linked to another SalesHive contact and its email or full first and last name matches; a changed email then updates that same record. A contact with no email syncs only to such a verified record. It is never created in HubSpot, its HubSpot email is left alone, and without a match it is skipped. A confirmed HubSpot merge follows the surviving record. Matching a secondary email keeps HubSpot's chosen primary email. For contact updates, name, company and phone similarity never choose an existing record. Calls for a prospect with no email follow their own stricter matching, described in the next answer. If a saved link is unavailable and neither the SalesHive ID nor email finds a match, SalesHive asks for review instead of creating a replacement.
How are HubSpot calls logged for a prospect with no email?
SalesHive logs the call on an existing HubSpot record it can verify and never creates a contact or company for it. It looks for a contact first: the saved HubSpot link, the SalesHive ID stored in HubSpot, a verified HubSpot Record ID saved on the prospect, then exactly one HubSpot contact with the same full first and last name and the same company name or direct or mobile phone. When it uses a contact, SalesHive saves its link and SalesHive ID on that HubSpot contact so later calls go to the same person; it does not change the HubSpot email. With no contact match, it logs the call on exactly one HubSpot company whose domain matches the prospect's company website or whose name matches the company name, with no conflicting name or domain. Otherwise the call is skipped and nothing is sent. Details says Call logged on HubSpot contact or company with the name and record number, or starts with Call skipped. and says why, for example several possible matches or a record that belongs to another SalesHive contact. Correct the prospect or the HubSpot record so the next call can be logged. If HubSpot does not confirm whether it created the call, the call fails instead of retrying, so it is never logged twice: check the record's activity in HubSpot first. This does not apply to hotel location connections.
Does Possible duplicate mean the sync failed?
Check Outcome and Details in Recent sync activity. With success, a name plus company or personal-phone match is an advisory warning and sync continued. Conflicting SalesHive IDs, an email already belonging to a different linked contact, or several records with the same SalesHive ID stop the affected update. Review the records in HubSpot, merge only if they are the same person, and otherwise correct the email or link. Then retry the affected failed records.
Will SalesHive create a second HubSpot meeting when my team already booked it in HubSpot?
No. When a meeting SalesHive syncs is already on the same HubSpot contact at the same time, and that HubSpot meeting came from HubSpot's meeting scheduler or HubSpot calendar sync, SalesHive uses your meeting instead of creating another. It adds its booking notes in a marked block and keeps the outcome up to date, but never moves the time or changes the title or invite, and it keeps an outcome your team already set, such as a no-show. If several HubSpot meetings match, or the matching meeting came from somewhere else, SalesHive changes nothing and creates nothing. Details in Recent sync activity then shows Possible duplicate with the HubSpot meeting IDs and time. Delete or merge the extra meeting in HubSpot, or ask your SalesHive team which one to use or to link it. The next update to that booking then syncs.
Why does Record owner ask me to disconnect and reconnect?
Your connection was made before SalesHive asked the CRM for permission to read its users. Disconnect and reconnect once to load the Assign new records to list. Until then, new records follow the CRM's own default assignment. If the box says the owner list isn't available for this CRM yet, reconnecting will not help.
What does Sync is retrying mean?
The connection is still on, but the CRM refused the last 3 or more sync runs (about 15 minutes), so nothing new is reaching it. SalesHive retries about every 5 minutes. Read the issue under the status card and open Technical details for the CRM's own message. If it says to reconnect, select Reconnect and sign in again. Last 24 hours can show no record failures meanwhile, because these failures happen before any record is sent.
Why does my HubSpot connection say Not syncing?
HubSpot refused SalesHive's sign-in, for example because the sign-in expired, or the HubSpot account or the SalesHive app install was removed. SalesHive stops trying instead of retrying every few minutes, and your SalesHive strategist is alerted. Select Reconnect and sign in to the correct HubSpot account to resume. Existing HubSpot records are not changed.
Are the sample prospects from our SalesHive demo sent to this CRM?
No. The fictional prospects created for your pre-sale demo (demo addresses ending in @example.invalid) and their calls, emails and meetings are never sent to your CRM, including during an initial import or a retry. They are also left out of Last 24 hours and Recent sync activity, so those reflect only your real contacts and activity.
Book a call

Let’s talk about your sales goals

Talk with our team about our services, pricing and how we can help your team grow.

Book a call

Choose a time to talk with our team.