Skip to content

SalesDrive ​

Connect SalesDrive and every lead your widgets collect turns into an order (заявка) in your CRM — with the contact, the conversation text, the products the visitor looked at and the UTM tags of the visit. No feed, no export, no manual copying.

The connection is one-way: Looma writes into your CRM and never reads orders or the catalogue back. If you need shop data in SalesDrive, that is a separate channel your shop already has.

What reaches your CRM ​

Leads from chat and search. Everything the AI assistant, the search widget and the widget forms collect. Each lead becomes one order in SalesDrive.

Updates to orders already sent. If a lead changes after it reached the CRM — a phone number that arrived later in the chat, a longer conversation — Looma updates the same order instead of creating a second one. Sending the same lead twice never produces a duplicate.

Leads without contacts are not sent

A lead with neither a phone number nor an email is skipped: it would arrive as an empty order nobody can call back.

Before you start ​

  • A SalesDrive account and the right to create an API key in it.
  • The Owner or Administrator role in Looma: the Integrations section is limited to those two.
  • An active subscription. An expired one redirects you to Billing before the page opens.

Step 1. Get the API key ​

In SalesDrive open Settings → General settings and integrations → Other services → API and create a key.

The key must be allowed to write orders

SalesDrive keys have permission levels. Pick one that allows orders: add, edit and read. A key that can only read may look fine but cannot deliver leads.

Note your account subdomain too. For the cabinet https://demo.salesdrive.me it is demo.

Step 2. Connect the site ​

  1. Open Integrations in the sidebar and pick the SalesDrive card.
  2. Find your site in the list and press Connect.
  3. Fill in Account subdomain — only the subdomain (demo), without https:// and without .salesdrive.me.
  4. Paste the API key and press Save.
  5. Press Test connection — the button appears once the key is saved.

The SalesDrive connection page lists all your sites, each with its own badge and button: Configure for a connected site, Connect for the rest. A site whose transfer was stopped also shows the reason in red and the last error returned by the CRM.

The SalesDrive connection page with four site rows: a Connected site with the Configure button, a site with the red Transfer stopped badge, an explanation and the CRM error 401 Unauthenticated, a site marked Not checked yet and a Not connected site, each with the Connect button

When the test succeeds, the badge next to the site name turns into Connected, a green Connection works label appears inside the form, and the settings appear below it.

The open connection form of a connected site: the instruction on where to get the key in SalesDrive, the Account subdomain field with its hint, the API key field with the hints "Saved. Enter a new value to replace it." and a warning about switching to another CRM account, the Save, Test connection and Disconnect buttons, and the green Connection works label

One key, several sites

SalesDrive has one rate limit per key, so sites that use the same key share it. Looma tells you when that happens — transfers get slower, nothing breaks.

Step 3. Choose what to send ​

There is no pipeline or source to pick: Looma sends the order and SalesDrive puts it where your own rules say.

SettingWhat it does
Country codedialling code without the + (default 380), digits only. Numbers written in national format are converted to international format with it
Leads from chat and searchthe main switch. Nothing is delivered while it is off
Also send the leads collected earlieroff by default. The form shows how many leads exist so far. Without it only leads created after you save reach the CRM — what you want if the older ones are already there by another route. With it, the whole backlog goes over at a steady pace

Press Save settings. Delivery starts within a minute.

The Where leads should go section: Country code 380 and the What to send block with Leads from chat and search ticked and Also send the leads collected earlier with the count of collected leads, plus the Save settings button

What an order contains ​

  • Contact — first and last name (split from the full name), phone in international format, email.
  • Comment — the lead text, followed by the products the visitor looked at.
  • Site — the name of your site.
  • UTM tags of the visit: source, medium, campaign.
  • Landing page and referrer.

Products travel as text lines in the comment, not as order items:

text
Товари з чату:
• Sofa Milano (SKU 39230) — 12 999 UAH

Each line has the name, the SKU and the price with its currency. SalesDrive does not receive product line items, so order totals in the CRM are not calculated from them; your operator sees what the visitor was interested in.

The comment is kept in sync with Looma

When a lead changes, the order's comment is rewritten with the current lead text. Put your own notes in SalesDrive's other fields and tasks, not in that comment. Looma updates only the contact and the comment — it never changes the order status, the UTM tags or anything your operators set.

Timing ​

New lead → order in the CRMabout a minute
Backlog transferroughly ten leads a minute per site
RateLooma paces itself and backs off when SalesDrive asks it to, without losing anything

When something goes wrong ​

The badge next to the site name tells you where you stand:

BadgeWhat it means
Not checked yetthe key is saved but never tested — press Test connection
Connectedeverything is running
The CRM rejected the keythe key is wrong, revoked or not allowed to write orders — check the key and its permission level
The key is correct, but the CRM grants no access to the datayour SalesDrive plan or key does not allow what Looma asks for
The CRM is not respondinga temporary SalesDrive outage or a mistyped subdomain; Looma keeps retrying
Transfer stoppedten consecutive failures — see below
Not connectednothing saved for this site yet
Beyond your plan limitthe site itself is over the plan's site allowance — see Billing

If a test shows The CRM is busy with other data right now — try again in a minute, just wait a minute and press Test connection again.

After ten consecutive failures Looma stops sending and emails the account owner. The site shows a red Transfer stopped badge and a note: Transfer stopped after several consecutive failures. Test the connection, then press "Retry failed" — the queue will resume. Below it you may see the last error the CRM returned. Nothing is lost: fix the cause, press Test connection, then press Retry failed. A success resets the counter.

If you press Retry failed while the transfer is still stopped, the leads are queued again but wait: the message says to press Test connection first.

The Retry failed block appears only when something is stuck, and shows what and why:

  • Rejected by CRM — the CRM refused the data itself.
  • Skipped — no phone and no email — nothing to create an order from. These cannot be sent, whatever you do.
  • No answer from the CRM — still in flight, usually clears on its own.
  • CRM rate limit — delivery stalled — SalesDrive is limiting the speed; this clears by itself and Retry failed does not speed it up.

A connected site with the open form: the warning that the key is shared with another site, the key field, the action buttons, the Connection works label and, at the bottom, the amber block "Rejected by CRM: 2 · Skipped — no phone and no email: 1" with the Retry failed button

Changing the key or the CRM account ​

Paste a new key on the same page and save. While a key is saved, the form warns you: if it belongs to a different SalesDrive account, everything already sent stays in the previous account and is no longer updated there. Only new leads go to the new account.

Disconnecting ​

Integrations → SalesDrive → Disconnect. You are asked to confirm, and the stored key is deleted, not just disabled.

Disconnecting clears the delivery history

That history is what remembers which leads have already been sent. Connect the same CRM again and previously sent leads arrive a second time, as new orders.

Troubleshooting ​

I cannot see the Integrations section. It is limited to the Owner and Administrator roles.

"The account address is just the subdomain, for example "demo"". Remove https://, slashes and .salesdrive.me from the field.

The settings do not appear. They show only after a successful Test connection.

"The stored key cannot be read. Enter it again." Paste the key again and save.

"Too many checks in a row. Try again in an hour." The connection test is rate limited to protect your SalesDrive key.

Phone numbers arrive malformed. Check the Country code field — without it numbers written in national format cannot be converted to international.

Everything is connected but nothing arrives. Check that Leads from chat and search is ticked, and that the leads you expect were created after you saved — the backlog only goes over if you tick Also send the leads collected earlier. Leads with no phone and no email are never sent.

Orders appear without products as items. This is expected: products are listed as text in the order comment.

  • Leads — where the leads come from
  • KeyCRM — the same connection for KeyCRM
  • Integrations — API keys and webhooks for your own systems
  • Billing — plans and subscription state

Looma.chat — AI-powered e-commerce search & chat