Documentation CRM DEALERSHUB

CRM integration

DEALERSHUB

DEALERSHUB integration overview
  • CategoryCRM
  • AuthNot available

Overview

DealersHub (dealershub.co.uk, AS Intelligence Ltd) is listed in MessageMind so dealerships can see it on the integrations screen. The 'Connect Dealers Hub' modal is shipped and takes a single field, API Key, so the card is clickable, but DealersHub has not yet published a partner API or a way to validate a pasted key. Until it does, the server refuses every key with one generic error and the card never reads as Connected. When DealersHub documents an API, the live probe will replace the current connect behaviour and no front-end change is needed.

Requirements

  • A DealersHub account.
  • A DealersHub API key, once DealersHub makes one available to partners.

How to connect

  1. In the MessageMind dashboard, open Integrations and click the DealersHub card. The 'Connect Dealers Hub' modal opens with the description 'Enter your Dealers Hub API key to connect your dealership to MessageMind.'
  2. Paste your key into the single field labelled API Key (placeholder: 'Paste your Dealers Hub API key'). The tooltip reminds you to treat the key like a password and never share it.
  3. Click to connect. Until DealersHub exposes a partner API, the server cannot verify the key and the connect call returns 'This Dealers Hub API key is not valid. Check the key and connect again.' Nothing is stored and the card stays disabled.

Authentication and permissions

Mechanism
API key. The field label on the card ('API Key') is the wire key the server reads, so it must stay byte-identical between the dashboard card and the server config.
Credentials
A single DealersHub API key, pasted into the password-type field on the 'Connect Dealers Hub' modal. The key is never persisted today because it cannot be proven.

Example workflows

What happens when you submit the connect card today

  1. You open the DealersHub card on /integrations and the 'Connect Dealers Hub' modal appears with the single API Key field.
  2. You paste a key and submit. The dashboard posts the keys map to the server.
  3. The server reads keys['API Key']. If the field is empty, it fails with reason MISSING_KEY. If the field is set, it fails with reason UNVERIFIABLE because DealersHub exposes no probe to validate the key.
  4. Both failure modes return the same message, 'This Dealers Hub API key is not valid. Check the key and connect again.', and nothing is written to your tenant.

Limitations

  • The current MessageMind DealersHub connector has no verified partner API connection, so there is no way to verify a pasted key.
  • Every connect attempt is refused with a single generic error (MISSING_KEY if the field is empty, UNVERIFIABLE otherwise); nothing is stored and the card never reads as Connected.
  • No data is read or written in either direction, because no connection is ever saved.

Troubleshooting

The 'Connect Dealers Hub' modal always says 'This Dealers Hub API key is not valid.'

By design. DealersHub does not yet publish a partner API, so the server cannot prove any key and refuses them all with the UNVERIFIABLE reason behind that message. The integration will become live when DealersHub documents a partner API; the live probe will replace the current refusal in dealersHub.connect without changing the card.

The DealersHub card stays disabled after I submit a key.

Nothing is stored on an unverifiable connect, so the card never flips to Connected. There is no action to take on the MessageMind side until DealersHub exposes a validation endpoint.

Disconnect and reconnect

  • There is nothing to disconnect: no key is stored for DealersHub in the current implementation.