Integrations
Marketplaces, websites, carriers, banks and payments, messaging: connecting multiple accounts and what they give you. · 32 articles
How it works
Marketplaces
PromThe Prom integration brings orders from your Prom account straight into “Deals”: the client is found by phone number or created, products are linked to the warehouse, and delivery and payment go into the deal card. Deals from Rozetka stores that work through Prom also come in via Prom; conversations with buyers go to “Conversations,” and stock and prices on Prom can be updated from your own warehouse.
RozetkaThe Rozetka integration uses the Seller API to bring marketplace orders into “Deals”, send the status and waybill back to Rozetka, pull buyer chats into “Conversations”, and create waybills for delivery to “Rozetka Stores”. Connecting takes one click: log in with your seller account username and password and click “Connect Rozetka” — settings, statuses, and order intake turn on by themselves.
KastaThe Kasta integration brings Kasta marketplace orders into “Deals” via the official supplier API and sends the order status and waybill back to Kasta. Connecting takes one click: enter the token and click “Connect Kasta”. Waybills for Kasta orders are free only when created through the hub.kasta.ua account — there's a separate “Kasta hub” card under “Carriers” for that; you can also ship directly with Nova Poshta or Ukrposhta, but it's paid (with a warning).
EpicentrThe Epicentr Marketplace integration brings orders straight into “Deals” via the official Merchant API: client, products, status — and the order status and waybill go back to Epicentr. Connecting takes one click: paste the “API key” and click “Connect Epicentr”. Stock levels on Epicentr are kept up to date by AI Anya.
OLXThe OLX integration uses the Partner API to bring buyer conversations into “Conversations”, lets you create a deal from an “OLX Delivery” conversation, and updates listings and prices from the warehouse. The OLX Partner API doesn't provide a separate order list, so a deal comes from a conversation rather than from polling, as it does with Prom or Rozetka.
MAUDAUThe “MAUDAU” card in “Integrations” connects Helomi to your MAUDAU marketplace seller account. Product listings for MAUDAU are created by AI Dasha and delivered as an XML feed; prices and availability come from our warehouse via the “Price list” feed, and the Public Merchant API username and password from the seller account are needed only when prices have to be sent via the API.
AlloThe Allo marketplace integration lists your products on Allo via a feed: AI Alla builds the listings from CRM data, and Allo reads the file at a permanent URL on its own — along with prices and stock. The “Allo” card in “Integrations” stores the account's username and API key, checks the login and balance, and shows the feed URL; you can have several Allo accounts.Websites and webhooks
Ключі API та вебхукиЩоб сайт, сервіс автоматизації (Zapier, Make, n8n), облікова програма чи ваш власний код працювали з Helomi, підключіть їх як «Зовнішню програму»: у неї свій ключ API, свої права й свій підпис у журналі. Спільного ключа на всю компанію в Helomi немає навмисно — так кожну інтеграцію видно окремо і кожну можна відкликати, не зачепивши решту. Якщо сервіс уміє лише надсилати заявки на адресу, замість ключа візьміть вхідний вебхук.
Websites (WooCommerce and others): accounts, fields, webhookThe “Websites” integration brings orders from your WooCommerce online stores straight into “Deals”. Each website is a separate card with its own toggle, webhook URL, source, assignee, status map, field mapping, and log. The simplest way to connect: on your website, replace the webhook URL with the “Webhook url” from the card — the fields are already linked, and the first order will turn the card on by itself.
WebhookThe Webhook integration connects Helomi with any service in both directions. Incoming webhooks receive data from a website, form, or other service (WooCommerce, Contact Form 7, Weblium, Facebook Leads via Apix-Drive, WIX) and, following your mapping, create a counterparty, a deal, and a task. Outgoing webhooks are triggers with a Webhook action: when an event happens in the CRM, the data goes to another service (SMS, Viber, Telegram, stock levels…).
Websites (WooCommerce and others): accounts, fields, webhookThe “Websites” integration brings orders from your WooCommerce online stores straight into “Deals”. Each website is a separate card with its own toggle, webhook URL, source, assignee, status map, field mapping, and log. The simplest way to connect: on your website, replace the webhook URL with the “Webhook url” from the card — the fields are already linked, and the first order will turn the card on by itself.WebhookThe Webhook integration connects Helomi with any service in both directions. Incoming webhooks receive data from a website, form, or other service (WooCommerce, Contact Form 7, Weblium, Facebook Leads via Apix-Drive, WIX) and, following your mapping, create a counterparty, a deal, and a task. Outgoing webhooks are triggers with a Webhook action: when an event happens in the CRM, the data goes to another service (SMS, Viber, Telegram, stock levels…).Carriers
Nova PoshtaThe Nova Poshta integration lets you create waybills right from a deal, print labels, see the parcel status, and automatically move the deal to a stage based on the delivery status. The settings mirror KeepinCRM: what to put on the waybill, how many packages and what dimensions, multiple senders (accounts) with their own keys and access rights, and the link between statuses and deal fields.
UkrposhtaThe Ukrposhta integration creates shipments from a deal via the eCom API, tracks them via the status API, and moves the deal to a stage based on the delivery status. The settings mirror KeepinCRM: multiple sender accounts, sender addresses, shipment lists (registers) with form 103A, additional services, and the link between statuses and deal fields.
MeestThe Meest integration creates shipments from a deal, prints labels, tracks parcels, and moves the deal to a stage based on the delivery status. The settings work like KeepinCRM: multiple sender accounts, each with its own contract and token, waybill form defaults, access rights, and the link between statuses and deal fields.
Rozetka DeliveryRozetka Delivery is Rozetka's delivery service: it's used to create waybills for Rozetka marketplace orders, including deliveries to “Rozetka Stores” pickup points. The card under “Carriers” holds the Rozetka account login, the sender, waybill defaults, access rights, and the link between delivery statuses and deal stages. For stores that sell through Prom, the waybill is created in the Prom account, not here.
Kasta hubKasta hub is the hub.kasta.ua supplier account used to create waybills for Kasta orders. It's the only free option: in that account, Kasta pays for delivery. You can also create a Nova Poshta or Ukrposhta waybill directly, bypassing the account, but you'll pay for it — Helomi warns you and asks for confirmation. The card under “Carriers” holds the account's username and password.Banks and payments
Checkbox (fiscal receipts)The Checkbox integration fiscalizes sales from deals: a manager clicks “+ Create receipt” on the deal card, and the Checkbox software cash register (PRRO) issues a fiscal receipt with the deal's products, the payment method, and the buyer's email. Multiple organizations (profiles) and cashiers are supported, along with access rights for creating receipts, refunds, and viewing and printing receipts; all receipts are collected in “Finance → Fiscal receipts”.
MonobankThe Monobank integration pulls the statement of a sole proprietor (FOP) account or a card into “Finance” via the bank's personal API: every transaction goes through import rules, an incoming payment with a deal number in the payment purpose becomes a payment on that deal by itself, and the rest wait for review in “Incoming”. You can have as many bank accounts as you like — each one connects as a separate account with its own token, wallet, and settings, and with instant transactions turned on, a payment shows up in “Finance” within a minute. Re-importing doesn't create duplicates.Monobank for Business (LLC, sole proprietor)The “Monobank for Business” integration lets you pay from a company or sole proprietor (FOP) account right from the CRM: you prepare a payment to a supplier, carrier, or partner, the CRM sends it to the bank as a draft, and the director signs it in the monobank app. Once signed, the payment becomes an expense in “Finance” by itself, with its basis — payment for a batch or a payout to a partner; without a person's signature in the bank, money never goes out. This is monobank's business API (a company or FOP account at web.monobank.ua), separate from the personal API the CRM uses to read the statement (the “Monobank” article): for one FOP account you may have two cards — “Monobank” (statement) and “Monobank for Business” (payments). A wallet without such a key (a personal card, cash) can also pay from the CRM — in “to be paid” mode (the “Finance” article, §7d).
PrivatBankThe PrivatBank integration imports the statement of a sole proprietor (FOP) or legal entity account into “Finance” via the “Autoclient” API of Privat24 for Business. Only transactions posted by the bank are taken, the category is matched by the payment purpose, and re-importing doesn't create duplicates.
NovaPayThe NovaPay integration pulls the statement of your NovaPay business account (sole proprietor or LLC accounts) into “Finance” and downloads cash-on-delivery registers every day: by waybill number, the payment becomes income on the deal, and the NovaPay fee becomes an expense with the basis “deal”. The register payout to your bank account is posted as a transfer from a transit wallet, so income isn't counted twice. Each NovaPay business account is a separate account with its own keys, wallet, and settings; the account token is single-use, and the CRM refreshes it by itself. Re-importing doesn't create duplicates.
LiqPayThe LiqPay integration creates a payment link for a deal that the manager sends to the client. Once the client has paid, the payment is posted as income on the deal in “Finance” by itself — once, with no duplicates.
MonoPay (Plata by mono)The MonoPay integration (Plata by mono acquiring) creates a payment link for a deal via monobank. The client pays by card using the link, and the payment is posted as income on the deal in “Finance” by itself — once, with no duplicates.
RozetkaPayThe RozetkaPay integration pulls buyer payments into “Finance” with no human involved: each payment becomes income on a deal by order number, the RozetkaPay fee is visible on every payment, and a refund becomes an expense on the deal. Payments arrive in two ways: the API transaction report every 30 minutes and an instant signed webhook. If the deal's income has already been recorded by a channel rule (Prom, Rozetka), there won't be a second income entry — the deal is just marked “paid via RozetkaPay”. A repeat of the same payment (webhook and report, a repeated webhook) doesn't duplicate anything.Messages
TelegramYour company's Telegram bot: a client writes to your bot — the conversation appears in “Conversations”, and replies from there go out through the same bot. Each bot (brand, store) is its own account on the card, with a token from @BotFather; the administrator connects it on their own, with no developer and no server setup. Telegram orders placed by AI Eduard become Helomi deals directly.
ViberYour company's Viber bot: client messages to your bot appear in “Conversations”, and replies from there go out through the same bot. Each bot is its own account on the card, with a token from the Viber bot panel; the administrator enters the token and turns on the webhook with a button, no developer needed.EmailThe “Email” integration connects your company's mailboxes to the Helomi “Email” section: emails arrive in the app, show up on the client card and in the deal, and you can reply right from there. Gmail, Google Workspace, Outlook, and Microsoft 365 connect by signing in with Google or Microsoft, no password needed; ukr.net, i.ua, meta.ua, and email on your own domain connect with a password, and the app fills in the servers by itself. Everything is done in the “Email” card in “Integrations”.
SMS (TurboSMS)The TurboSMS integration sends SMS to clients, just like in KeepinCRM: automatically when a deal moves to a chosen stage (a template with variables — waybill, amount, name, receipt link), manually from the deal card, in bulk from selected deals, and from a trigger. Sender names, templates, balance, a test SMS, and a sending log with delivery status are all in one card; you can connect several TurboSMS accounts, and everything is set up by hand, no developer needed. AI employees work with the same settings through their own tools.
BlackBoxBlackBox is a database of buyers who order and don't pick up their parcels. The integration checks every deal by phone number by itself and shows the result as a banner on the deal card (with “Check again” right there), and you can add a buyer who didn't pick up a parcel to the database yourself, from the deal. BlackBox requests are limited, so today's remaining quota is shown on the card.AI and more
Model keys (Anthropic, OpenAI, Kimi, Gemini)The “AI” tab in “Integrations” is where an organization connects its AI employees and language model keys: Anthropic (Claude), OpenAI (ChatGPT), Moonshot (Kimi), Google (Gemini). The platform doesn't lend out its own keys: requests go through your key and at your expense, and usage is shown in each AI's dashboard. You can also work without an API key — connect your own subscription chat via a session file.
KeepinCRM (migration)The KeepinCRM card is needed while you move from the old CRM to Helomi. A mirror runs through the KeepinCRM API key: every 5 minutes, deals, clients, products, payments, tasks, and deliveries from KeepinCRM are pulled into Helomi without duplicates, while AI agents that haven't been moved over yet read from and write to KeepinCRM. Sales channels are switched over to Helomi one at a time.
Vchasno“Vchasno” is an electronic document management service: signing and exchanging documents with counterparties online. An integration with it is planned so that Helomi documents go into electronic document flow without being transferred by hand.