Connect GlassHive
GlassHive is a CRM built for MSPs. Connect it to Current and your companies, contacts, opportunities, activity, tasks and lists come into Current and stay in step in both directions. Current reads GlassHive every 10 minutes, and a Tenant Admin can press Sync now for an immediate pass.
What syncs, and which way
| In GlassHive | In Current | Direction |
|---|---|---|
| Companies | Companies | Both ways |
| Contacts | Contacts | Both ways |
| Opportunities | Deals on the GlassHive board | Both ways |
| Notes, calls, meetings and emails | Notes & activity on the company | Both ways |
| Tasks | To-dos | Both ways |
| Lists and their members | Contact lists | Both ways (a member removed in Current stays on the GlassHive list) |
| Form submissions | Website leads | Into Current only |
| Campaigns | Campaign history on the GlassHive card | Into Current only |
| Collaterals | Collateral library on the GlassHive card | Into Current only |
| Users | Matched to the people in your workspace | Into Current only |
| Solutions and opportunity line items | Line items shown on the deal | Into Current only |
Text messages, bounces, opens, clicks, spam reports, blocks and unsubscribes are counted but not imported: they are marketing events, not conversations. Line items come in without cost or margin; cost stays in GlassHive.
Set it up
Connecting is a Tenant Admin action. Open Integrations, go to Sales & marketing, find the GlassHive card and press Set up. The setup walks through each step on its own screen, and you can come back to any of them later to change a mapping.
- 1Paste your API keyCopy an API key from your GlassHive account and paste it in. The key is stored server-side and never shown again.
- 2Check the connectionCurrent asks GlassHive who the key belongs to and shows the account name. A refused key fails here, before anything is read.
- 3Match your peopleEach GlassHive user is matched to a person in your workspace by email. Pick the right person for anyone left unmatched. Tasks assigned to an unmatched user are skipped until you do.
- 4Map your stagesGlassHive has no list of opportunity statuses to read, so Current lists every status it has seen, with how many opportunities use it and a sample name. Pick the board the deals land on (or create one) and map each status to a stage. Choose whether an opportunity's price fills the deal's monthly value or its one-time value.
- 5Review the companiesCurrent lists every GlassHive company with what it matched in Current. Confirm the ones that need a decision: link to an existing company, create a new one, or leave it in GlassHive.
- 6Choose what happens to custom fieldsMap each GlassHive company or opportunity custom field to a Current field, create a new one, or ignore it.
- 7Start the importPress Start import. Current brings records across in order (people, companies, contacts, opportunities, activity, tasks, lists, form submissions, then the read-only libraries) and the card shows progress for each. You can leave the page; it carries on.
How companies are matched
For each GlassHive company Current looks, in order, for a company already linked to it, then for exactly one Current company with the same website domain, then for exactly one with the same name. If nothing matches, it becomes a new company at import. If two or more Current companies could be the one, it waits in the company review for you to choose, and it and its contacts are not imported until you do.
When both sides change the same record
The last edit wins. If only GlassHive changed a record since the last sync, Current takes GlassHive's version. If only Current changed it, Current sends its version (once sending is on, see below). If both changed, the later edit wins, and a tie keeps Current's. The sync log records which side was kept.
Your PSA keeps the fields it owns. On a company your PSA manages, GlassHive never changes the name, phone, website, address or whether it is a customer. On a deal linked to an opportunity in your PSA, GlassHive never changes the name, stage, status, amounts or close date. Billing, contracts, recurring revenue and sync ids are never touched in either direction.
Sending changes to GlassHive starts off
Reading and the import work as soon as the key is connected. Sending changes made in Current back to GlassHive is off until a Tenant Admin opens Manage on the GlassHive card and turns on "Send changes made in Current to GlassHive". Only changes made after you turn it on are sent. Before Current creates a company or contact in GlassHive, it searches GlassHive for it first (by website or name, or by email for a contact) and links to the one it finds instead of making a duplicate.
The GlassHive rate limit
GlassHive allows 10 requests a second for each API key, and it can disable an account that keeps going over that limit. Current sends at most 5 requests a second for your workspace, spaced out evenly, so it never comes close. If GlassHive still asks Current to slow down, Current waits as long as GlassHive says (or backs off by itself when GlassHive gives no time) and picks up again on the next run. A large account takes a while to import for this reason; the card shows how far it has got.
Things to know
- +One CRM at a time. A workspace connects GlassHive or HubSpot, not both. Disconnect HubSpot before connecting GlassHive, and the reverse.
- +Records that come from GlassHive never go to your PSA on their own. A company, contact, deal or note that arrived from GlassHive stays in Current and GlassHive.
- +Deletes do not cross in either direction. A record deleted in GlassHive is marked as gone on its link and stays in Current. A record deleted in Current stays in GlassHive.
- +A deal the sync moves to won or lost does not create commission. Commission comes from a deal your own team closes in Current.
- +Custom field values are read from GlassHive and never written back, because GlassHive's API cannot write them. Contact custom fields stay in GlassHive.
Moving to Current for good? See "Switch from GlassHive to Current". If something is waiting or skipped, see "GlassHive: fixing common sync problems".
