OneBox CRM Integration

The OneBox CRM integration lets your AI sales assistant turn a conversation into a OneBox lead or deal (in OneBox both are orders in a workflow). The assistant finds or creates the contact by phone, writes the order into the workflow you choose, sets its status, and on deals adds products, a delivery method, a payment method and a Nova Poshta branch.

At a glance

You need	Where	Result
Your OneBox address, login and REST API password	Your OneBox account	Credentials to paste into MyChatBot
The credentials connected to an assistant	MyChatBot → Integrations → OneBox CRM → Submit	"OneBox CRM connected successfully"
Workflows and fields selected	Entities & Data Fields Configuration → Apply fields	The assistant knows where to write and what to fill
Statuses synced	Funnel Status Sync → Sync statuses	The assistant uses your real statuses

What your assistant can do

Action	What happens
Create a lead	Finds the contact by phone or creates one, then creates an order in your leads workflow. The order is named <customer name> - <source> and its description holds a link to the chat.
Update the lead	Updates the lead the assistant created for this customer earlier, for example its status or address.
Create a deal	Like a lead, in your deals workflow, plus the products the customer chose and the delivery and payment methods.
Update the deal	Updates the deal the assistant created for this customer earlier.
Add or update the contact	Saves the customer's name, phone and birthday on the OneBox contact without touching an order.

The assistant reads only what it needs to fill in the order: your product catalogue, your order sources, and your delivery and payment methods. It doesn't look up existing orders, stock or a customer's history there.

What data the assistant writes

• Contact: full name, phone and birthday (YYYY-MM-DD or DD.MM.YYYY). An email is saved on the order, not on the contact. The full name is read surname first: Shevchenko Taras Hryhorovych becomes last name, first name and middle name. A single word is saved as the first name.
• Order fields: order name and description, client name, phone, email and address, delivery note and the check total.
• Status: a status name from your synced list, or a OneBox status ID.
• Delivery and payment: a method's ID, or its name as it appears in OneBox.
• Products (deals only): each product's name, price, quantity and, when the assistant knows it, its article (SKU). The article is saved on the order line as the OneBox article and shows in the Арт. column, even when your catalogue has no such product. The assistant then links the line to a catalogue product: by article first, then by OneBox product ID, then by that ID read as an article, then by name. Each step runs only when the ones before found nothing. The name match ignores case and extra spaces, and treats Latin and Cyrillic look-alike letters as the same letter (such as a Latin o in кушoн). When a catalogue product is linked, its ID and article are copied onto the line, and if the price is 0 the catalogue price is used.
• Source: set when OneBox has a source named exactly like the channel or AI-<assistant name>.

Only the fields above are saved

The field picker may list more OneBox fields, including custom ones. Today the assistant writes only the order fields listed here. Every field you tick becomes something the assistant must collect, so ticking a field outside this list makes it ask for data that won't reach OneBox.

Get your OneBox credentials

You need three values:

• Domain — your OneBox address including https://, for example https://yourcompany.1b.app.
• Login — the OneBox user the assistant will act as.
• Rest API Password — the REST API password of that user. It's set separately from the sign-in password; if you can't find it in the user's settings, ask your OneBox administrator.

Use a dedicated OneBox user for the assistant, so its changes are easy to tell apart in OneBox's history.

Connect OneBox in MyChatBot

In the app

Go to Integrations — app.mychatbot.app/integration?integration=OneBox. Pick the assistant in the header dropdown first.

1. Select the assistant you want to connect.
2. Under Available Integrations → CRM Systems, pick OneBox CRM.
3. Fill in Domain, Login and Rest API Password.
4. Click Submit. On success you see "OneBox CRM connected successfully"; if the credentials are wrong, MyChatBot says it failed to get a token from OneBox.

Set it up

Workflows and fields

1. Under Entities & Data Fields Configuration, turn on Use Leads and/or Use Deals.
2. Pick the OneBox workflow for each: Select Leads Pipeline and Select Deals Pipeline.
3. Tick the fields the assistant may fill (see the list above).
4. Under Phone Lead/Deal/Entity Settings, turn on Lead Phone Required or Deal Phone Required if every order must carry a phone number.
5. Click Apply fields.

Statuses

Click Sync statuses under Funnel Status Sync. MyChatBot learns your statuses from your 200 most recent orders in the leads workflow (or the deals workflow, if you don't use leads). Re-run it after you change statuses in OneBox.

Nova Poshta address

When you tick the client address field, the assistant also collects the Nova Poshta city, region and branch. It checks the branch against the Nova Poshta directory and saves the address as City, <branch name from the directory>.

Guide the assistant

When the customer has chosen products and confirmed delivery, create a deal in OneBox
with status "New order", delivery "Нова пошта" and payment "Накладений платіж".

For every product, pass its article (SKU) from the catalogue or product feed.

Always ask for the Nova Poshta city and branch number before creating the deal.

When the customer only leaves a phone number to be called back, create a lead instead.

Use the delivery, payment and status names exactly as they appear in your OneBox.

Limits and requirements

• PRO plan or higher is needed to connect.
• One CRM per assistant. While OneBox is connected, the other CRM systems are grayed out for that assistant.
• Every field you tick is required, on updates too. Tick only what the assistant can collect in a chat.
• New statuses need an order first. Sync reads statuses from existing orders, so a status no order has used yet isn't offered. Put one order into it in OneBox, then sync again.
• Delivery and payment names must be unambiguous. If a name matches none or several methods, nothing is saved and the assistant is told which names are valid.
• An unrecognised Nova Poshta branch blocks the order. The assistant has to ask the customer again. If the Nova Poshta directory itself is unavailable, the address is saved as the customer gave it.
• One contact per phone. An existing contact with the same phone is updated with the new name and details, not duplicated.
• Products are added on create only. To change the products on a deal, edit it in OneBox.
• No webhooks. Changes you make in OneBox don't flow back into MyChatBot automatically.

See also

• Integrations CIS — the other regional CRMs
• Integrations overview — the connect flow every integration shares
• Orders — native orders and how external CRM orders show up in analytics