Elbuz pulls SalesDrive orders into sales documents and the catalog and stock from its YML export: sales, inventory and documents in one place, no retyping.
When you need this:
- Managers use SalesDrive — new orders appear in Elbuz in seconds.
- The CRM has history — the first API import moves it in pages, no duplicates.
- The catalog is in SalesDrive — products and stock come from the feed; order lines match their cards at once.
- A CRM status changed — the document updates payment and delivery, keeping the manager's status.
Where to start: get the YML export link and API key in SalesDrive, then create a “CRM SalesDrive” template.
What the SalesDrive connection does
The connection works over two channels at once: orders arrive via webhook and , the catalog comes from a YML feed.
- Instant order intake — the itself sends an order to Elbuz as soon as it's created or changed.
- History transfer — the API key fetches all old orders page by page and picks up whatever the missed.
- Your edits are protected — the total, customer, line items and of a document aren't overwritten after it's created.
- Catalog and stock from the YML export — products go to the base catalog, and order lines are matched to them by .
- Customers and cards for unknown products — contacts and a service category are created automatically.
What you need from SalesDrive
| Where in SalesDrive | What to do |
|---|---|
| «Установки» → «Товари/Послуги» → «Експорт YML» (Settings → Products/Services → YML export) | copy the export link |
| «Установки» → «Загальні налаштування і інтеграції» → «Інші сервіси» → «Webhook» (Settings → General settings and integrations → Other services → Webhook) | paste the webhook URL from Elbuz |
| «Установки» → «Загальні налаштування і інтеграції» → «Інші сервіси» → «API» (Settings → General settings and integrations → Other services → API) | create a key with the «Заявки — читання» (Orders — read) permission |
Elbuz pulls orders and changes nothing in the CRM, so the key only needs permission to read orders. Don't give the integration more rights than that.
How to connect
- Create a template of the “CRM SalesDrive” type and save it — the webhook URL appears only for a saved template.
- Paste the YML export link, the account subdomain and the API key.
- Copy the webhook URL and enter it in the SalesDrive settings; in the “Order intake (Webhook)” card, select the “Use webhooks” checkbox.
- Run the catalog import first so the products are already in Elbuz, and only then turn on orders: order lines will find their cards right away instead of creating half-empty duplicates.
- Look over the first orders — line items, total, customer, delivery service. If every document arrived with the same status, fill in the mapping tables (which ones).
What comes over with an order
| SalesDrive data | Document field in Elbuz |
|---|---|
| external order number | Document number |
| creation and modification dates | Order date, modification date |
| contact's first, middle and last name | Customer full name |
| contact's phone and email | Phone, email |
| amount due | Document total |
| comment | Order description |
| order status | Document status (via mapping) |
| payment method | Payment type (via mapping) |
| delivery service, waybill status | Delivery type, delivery status |
| waybill number, city, address, branch | Delivery details |
| line items: name, SKU, price, quantity | Document lines |
Order statuses, payment types and delivery services arrive as SalesDrive codes. Map them to your own lists with the buttons in the “Related settings” card of the template form — these are separate tables: order statuses, and separately delivery statuses, payment statuses and payment types.
If an order line has a discount — as a percentage or an amount — Elbuz recalculates the line price right away, with that discount applied. So the line price in Elbuz can differ from the product's “base” price: it's the price the item actually sold for.
Customers and the service category
Customers. Each order looks for a contact by email, then by phone, then by the SalesDrive contact ID — and creates a new one in the “Customer” group if nobody is found. If the order has a SalesDrive contact but no email or phone, Elbuz also creates a new contact and links it to that contact's ID.
The “End consumer” service contact gets only orders with no contact, email or phone: it's created once and then receives all such documents. If you delete “End consumer”, it comes back on its own with the first such order.
A category for unknown items. If a product from an order line isn't found in the catalog, Elbuz creates a card for it and puts it in the service category “Products - salesdrive - your template name”. The category is created disabled and excluded from exports; the next run finds it by name and puts cards there too.
- A deleted contact goes to the Trash first. A new order with the same email or phone finds that very contact again. Deleting a contact permanently doesn't break documents: their lines, totals and customer name stay, only the link to the card disappears.
- Delete the service category only when it's empty — deleting a category also deletes the products for which it's the main one. Lines of already imported documents aren't affected: the document keeps the name, SKU, price and quantity in its own fields. How to sort things out is in the data import overview.
How orders arrive and what a repeat run does to your edits
Most connections in Elbuz use polling — Elbuz periodically asks the marketplace whether there's anything new. SalesDrive uses a webhook (the same way orders from Shopify and Wix come in): the CRM itself knocks on Elbuz's door as soon as an order is created or changed. The order appears in Elbuz within seconds, not on a schedule.
The webhook URL contains a secret key that Elbuz generates the first time the template form is opened — that's how it knows which template to put the order into. So don't publish the URL anywhere other than the CRM's own settings.
Both channels mark orders with the same source, so an order arriving via both webhook and scheduled import isn't doubled: Elbuz recognizes it by the internal SalesDrive order ID and uses the same document. The webhook catches the live flow; the scheduled import picks up anything lost (say, while Elbuz was down) and moves the history on first connection.
- Start or end
- Action or result
- Decision: the path depends on the answer
What a repeat run does to your edits
The same order reaches Elbuz more than once: first via webhook, then the scheduled import may bring it, and after a change in the CRM — the webhook again. There's still only one document: Elbuz looks it up by the internal SalesDrive order ID together with the source code salesdrive.
| What's in the document | What a repeat run does |
|---|---|
| Total, customer name, phone, email, comment, city, address, branch, waybill number | Doesn't change them: they're written only when the document is created |
| Document lines — names, prices, quantities | Doesn't change them, even if they were later changed in the CRM |
| Payment method, delivery service, delivery status | Brings them in line with the CRM |
| Payment status | Doesn't change it: a SalesDrive order doesn't send it |
| Your status | Changes it only if the status in the CRM differs from last time |
| The order's own status | Stores it in the “Document status (site)” column of the order list |
| Any field of a posted document | Doesn't change it |
Not every channel updates an existing document:
- a webhook about a new order only creates a document that doesn't exist yet;
- a webhook about a status change in the CRM updates the document as shown in the table above;
- the scheduled import updates when the “Import orders from date (YYYY-MM-DD)” field in the “Advanced” block already has a date;
- the first history transfer (“Advanced” fields empty) doesn't touch existing documents — it only adds new ones.
The waybill number, city and address are taken from the order only when the document is created. If a CRM manager issues the waybill after the order has arrived, enter the number in the document by hand. Same with the total and line items: add a product to the order in SalesDrive, and the Elbuz document stays unchanged.
An unmapped status breaks nothing. If the mapping table has no row for an order or payment status, the document keeps what it already has. Payment type and delivery type are never empty: without a mapping row Elbuz picks them by the name from the CRM, and if that fails too, it sets the default value.
The status mapping table applies at the moment an order is received: if you fill it in later, already imported documents aren't reprocessed — change their status by hand.
Post the document: an import doesn't change any field of a posted document. You can see this in the “Posting status (signatures)” column. The general “who overwrites whom” breakdown is in the order import overview.
How to import the catalog and stock
Products from SalesDrive don't come via the API but as a regular YML feed: you paste the export link from your account, and Elbuz reads it like any other XML price list. You can open the feed in a browser and see exactly what the CRM returns.
The main benefit of this channel is line matching. In a SalesDrive order every line has a «ID товару/послуги» (product/service ID) field, and that's where the ID from the feed goes. When the catalog and orders come from one source, lines are matched to your cards automatically, with no guessing by name.
The feed goes to the base catalog — the “Products” window, not supplier price lists. A card is recognized by the feed's offer ID: on a match, stock, price, category, SKU, name and description are updated; otherwise a new card is created. Extras are enabled in the “What to import” section: “Import attributes”, “Import photo”, “Fill the manufacturer list”.
One template run does both jobs in turn: first it reads the YML feed, then it goes to the API for orders. An empty link field means “don't import the catalog”, an empty API key means “don't import orders”.
- Start or end
- Action or result
- Decision: the path depends on the answer
The catalog won't go to your storefront or marketplaces on its own — that takes a separate “Data export” (when imported data moves on).
What's gone from the feed
If an item disappears from the YML export, by default its card stays in the catalog with the last price and stock, with no log line. The “Delete entries in the base catalog that are not in the imported file” checkbox in “What to import” changes that; for SalesDrive it works, since the catalog is a feed. How it deletes: the data import overview.
The selection isn't limited to this source: it also catches products you created by hand or imported elsewhere, plus categories missing from the feed. Turn it on only when the SalesDrive feed is the sole source of your catalog. Imported orders aren't affected: a document line keeps its name, SKU, price and quantity in its own fields.
Scheduled updates and turning it off
The SalesDrive API has strict limits: about 10 requests per minute, 100 per hour and 1,000 per day. Elbuz fetches orders in pages of 100 with a 6-second pause between pages, so a bulk history import is slow. Set the scheduled import no more than once every 15 minutes: the webhook catches the live flow anyway.
The template card header has an “Active” / “Disabled” badge, and the order intake section has a “Use webhooks” checkbox. They turn off different things.
1
State pill: Disabled- State pill — Disabled takes the template off the schedule and stops webhook intake.
| What you did | What stops working |
|---|---|
| Switched the badge to “Disabled” | the scheduler no longer picks up this template, and the webhook stops being accepted too: Elbuz won't record an order from SalesDrive |
| Cleared “Use webhooks” | the webhook isn't accepted, the schedule works as before |
| Removed the API key | orders aren't fetched via API, the catalog still imports from the feed |
| Removed the YML export link | the catalog isn't imported, orders are still received |
When the template is disabled or the checkbox is cleared, Elbuz doesn't respond to the CRM's call at all and writes nothing to the log: on the SalesDrive side the delivery looks successful, but the order isn't in Elbuz. So after disabling a template, check the order list, not the webhook report on the CRM side.
Turn it back on, and the keys, checkboxes, schedule and webhook URL are all in place — nothing to change in the CRM. The webhook won't resend orders sent during the downtime, but the API import picks them up: it takes orders changed after the date in “Import orders from date”. The “Import” button works on a disabled template too (disable or delete a template).
How to check a run and fix a mistake
The import log opens in the Operations Center — the right-hand panel that doesn't block your work: you can close the template card, and the run won't stop.
| Log line | What it means |
|---|---|
| “SalesDrive: orders page 2 of 5, total loaded: 200” | how many API pages have been read and how many orders from them have been processed |
| “Orders received: 100” | how many orders this page brought — new and already known together |
| “Total orders imported: 12” | how many of them became new documents; the rest were already in the database. No line means nothing new |
| “Total items imported: 3” | how many cards had to be created for lines not found in the catalog |
| “SalesDrive: API error — …” | a red line with the CRM's rejection text; the run stops there |
| “Data import completed!” | the end of the run, with the time it took next to it |
In the order list, intake is confirmed by the “Source: name” column (your template name) and the “Source: code” column with the value salesdrive. Four more are useful next to them:
- “Document number (site)” — the order number in the CRM;
- “External document ID (UUID string)” — its internal ID, by which the document is recognized on a repeat run;
- “Date added (source)” and “Updated date (source)” — the dates of the order itself, not of the import.
If a column is missing, turn it on in the window's column settings. Look for an order that came via webhook in the same place: a webhook doesn't show an operation card with a summary.
If a run broke off
Each page of 100 orders is read from the API and saved to the database at once, and the “how far it got” marker moves with it — the “Import orders starting from ID” and “Import orders from date” fields in the template's “Advanced” block. So a break splits the work in two: pages read are already documents, the rest wasn't reached.
1
Import orders starting from ID2
Import orders from date- Starting from ID — shows how far order download has got.
- Starting from date — the scheduled download takes orders changed since this date.
Repeating is safe: an order that's already a document is recognized by its ID and doesn't create a second one. So the response to a break is simple — run the import again.
- Elbuz waits 30 seconds for the CRM to connect and up to 120 seconds for a response. If it times out or gets a rejection, you see the red line “SalesDrive: API error —”, and the run stops; this connection doesn't retry.
- The stop button on orders takes effect between pages: Elbuz finishes reading and writing the current page and doesn't take the next one.
If the wrong data was imported
The most common reason is a first run with the mapping tables not filled in: the orders arrived, but all with the same status. The cure isn't re-importing, but filtering and deleting.
- In the order list, filter “Source: code” by the value
salesdriveand add a filter by “Date added” — you get exactly what this connection created on a given day. - Select the rows and delete them in a batch. Right after deletion you see the message “Documents deleted: N” with an “Undo” button that brings back the whole batch with its lines. If you missed it, the batch stays in the “Document trash” (the window menu) for 30 days.
- In the “Advanced” block, clear the “Import orders starting from ID” and “Import orders from date” fields, save the template and run the import again — orders will now come through the filled-in mapping tables. Without this step, deleted orders won't come back on their own: the “how far it got” marker has already moved.
Posted documents aren't included in the batch: you get “Posted documents were not deleted (N). Cancel the posting first.” This is intentional — deleting a posted document wouldn't roll back the contact's turnover or the reservation.
Scenarios
CRM orders become documents, you maintain the catalog in Elbuz yourself
Fill in “SalesDrive account” and “API key”, leave “API URL” empty, enter the webhook URL in SalesDrive, and select the “Use webhooks” checkbox in the “Order intake (Webhook)” card. A template run then doesn't read the feed and only imports orders via API, while new orders from the webhook become sales documents.
The catalog isn't updated in this case. Elbuz looks for an order line among your cards by name together with SKU, then by name alone; if nothing is found, it creates a card in the service category.
Transfer order history when connecting
Fill in “SalesDrive account” and “API key”, leave “Import orders starting from ID” and “Import orders from date (YYYY-MM-DD)” under “Advanced” empty, and run the template. Orders arrive in pages of 100 with a 6-second pause, each page is saved before the next is requested, and the “Advanced” fields fill in on their own. Existing documents aren't changed.
If you don't need the history from the very beginning, enter in “Import orders starting from ID” the internal SalesDrive order ID up to which (inclusive) nothing should be transferred, and leave the date field empty: the run starts from the next one.
Statuses and payment from the CRM reach the document, while the manager keeps their own status
In the “Related settings” card, fill in the “Order statuses” and “Delivery statuses” tables, then turn on the webhook and a scheduled import. When an order changes in the CRM, the document gets the new payment and delivery; your status changes only if the CRM status differs from last time. Total, line items, customer and waybill number stay as created; posted documents aren't touched.
The Elbuz catalog fully mirrors the SalesDrive feed
Paste the YML export link into “API URL” and, in the “What to import” section, select the “Delete entries in the base catalog that are not in the imported file” checkbox. Products and categories missing from the feed are physically deleted — including cards you created by hand (what's gone from the feed). Already imported documents aren't affected.
What to do when orders don't arrive
| What you see | Why | What to do |
|---|---|---|
| The order is in SalesDrive but doesn't appear in Elbuz | The webhook URL was copied incompletely or not entered in SalesDrive; the template is disabled or “Use webhooks” is cleared | Copy the URL including the key at the end and check the template state (what turns off what) |
| “SalesDrive: enter the account and API key to download orders” | The key is filled in, but the “SalesDrive account” field is empty | Enter your account subdomain (connection fields) |
| The run only did the catalog, nothing about orders in the log | The “API key” field is empty | Create a key in SalesDrive and paste it into the template (where to get it) |
| “SalesDrive: API error — …” about exceeded limits | The schedule runs the import too often | Set the schedule to no more than once every 15 minutes (limits) |
| Order lines aren't matched to the catalog | The catalog in Elbuz came from a different YML export: the IDs differ | Import the catalog from the SalesDrive feed (catalog and stock) |
| All orders arrived with the same status | The status mapping table isn't filled in | Fill in the table and re-import the period (how) |
| A waybill issued in the CRM isn't in the document | The waybill is taken only when the document is created | Enter the number by hand (what gets updated) |
FAQ
What permissions does the SalesDrive API key need?
Reading orders is enough («Заявки — читання», Orders — read): Elbuz pulls data and changes nothing in the CRM. You create the key under Settings → General settings and integrations → Other services → API.
Why a webhook if there's an API key?
The webhook brings orders instantly, while the API key moves the history on first connection and picks up anything that may not have come through. The same order isn't doubled (how the channels work).
Why is the history import so slow?
Because of SalesDrive limits — about 10 requests per minute. Elbuz pauses between pages, so a large history is transferred gradually (limits).
Where do products come from — also via API?
No, the catalog and stock come from the SalesDrive YML export, whose link goes into the “API URL” field. That's also what gives exact matching of order lines.
Will a repeat import overwrite my edits to an order?
No: the total, customer, comment, address, waybill and line items stay yours, and your status changes only after the status changes in the CRM. A posted document doesn't change at all (field table).
I imported orders by mistake — how do I remove them?
Filter the order list by “Source: code” = salesdrive and delete in a batch; the “Undo” button and the “Document trash” bring back what was deleted (step by step).
Where it is and who has access
- Menu
- Directories → Operations → Data import
- Template type
- “CRM SalesDrive”
- Access right
- the “Import” window in “Group permissions”
- Have ready
- the YML export link, your account subdomain and a SalesDrive API key
The template's “Connection” card has three fields, each responsible for its own channel:
| Field | What it's for |
|---|---|
| API URL | The product YML export from SalesDrive — catalog and stock |
| SalesDrive account | Your account subdomain (for example mycompany) — needed to import orders via API |
| API key | The key for reading orders — order history and picking up changed ones |
The form also has a separate field with the webhook URL: Elbuz generates it for you, so you only copy it (just click the field) and paste it into the SalesDrive settings.
1
API URL: link to the YML export2
SalesDrive account (subdomain)3
API key for order download- API URL — the link to the YML export from SalesDrive; it carries the catalog and stock.
- SalesDrive account — the subdomain of your SalesDrive account.
- API key — used to download orders.
Related topics
- If you need the big picture of how orders from different systems become documents — Order import via API.
- If products from the feed need to reach your site or a marketplace — When imported data moves on.
- If you need to post an order and reserve the product — Customer order.
