# Horoshop + Krokul CRM

Yes, natively. Krokul CRM receives orders from an online store on Horoshop by webhook or by polling the API. An order becomes a deal with items from your catalog, and the buyer becomes a contact. The order status syncs both ways, and stock and prices from the Krokul warehouse go back to the store.

**Status:** Native. **Automation platforms:** Zapier.

## What your team gets

### A new order lands in a deal at once

Horoshop sends the order to the Krokul connection address as soon as the buyer places it. Krokul creates a deal «Horoshop #…» in the chosen pipeline and matches each order item to a Krokul catalog item by SKU. The stock reservation is made the same way as for a deal a manager creates.

### The same order status in the store and in Krokul

A manager moves the deal to another stage, and Krokul changes the order status in Horoshop. If the status changes in the store admin, the Horoshop webhook about an order status change moves the deal to the matching stage. You map stages to statuses in the connection settings.

### Stock and prices from one warehouse

Krokul sends Horoshop the stock level and price of an item when they change in the Krokul warehouse or price list. The store does not sell items that are physically out of stock, and the manager updates a price in one place.

### A returning buyer without a duplicate

Krokul checks the phone and email from the order against existing contacts, and the Horoshop customer update webhook refreshes the contact data. The Horoshop order number is the external key of the deal, so the webhook and polling together never create two deals.

### A store whose plan has no webhooks

If the plan offers no webhooks, Krokul polls orders through the Horoshop API with the API login and password. The first pass only remembers the latest order, so a fresh pipeline does not fill up with the whole store history. A separate switch lets you import the history.

## What moves between Horoshop and Krokul

| Horoshop | Krokul | Direction | When |
|---|---|---|---|
| Order (number, amount) | Deal «Horoshop #…» with an external key | Horoshop → Krokul | Store webhook or API polling |
| Order items (SKU, quantity, price) | Deal lines with catalog items | Horoshop → Krokul | Together with the deal |
| Buyer (name, phone, email) | Contact, found or new | Horoshop → Krokul | Together with the deal and on the customer update webhook |
| Order status | Deal stage | Horoshop ↔ Krokul | A stage change in Krokul or the status change webhook |
| Order comment | Entry in the deal feed | Horoshop → Krokul | New comment webhook |
| Item stock and price | Krokul warehouse and price list | Krokul → Horoshop | Stock or price changes |

## How to connect today

### Connect in the Marketplace

1. In Krokul, open «Marketplace» → «Horoshop» and click «Connect». Krokul shows an address like https://app.krokul.com/ingress/horoshop/<token>.
2. Pro plan: in the Horoshop admin, add this address to the webhooks for order status change, customer update and comment. Krokul fetches new orders by polling the API.
3. For the reverse direction and for plans without webhooks, fill in the store address and the Horoshop API login and password in Krokul. The password is stored encrypted.
4. Choose the pipeline, source, owner and the warehouse for stock, and map deal stages to order statuses. Every received order and every store update is visible in the connection log.

### Through Zapier

1. The Horoshop trigger New Order or New User in Zapier.
2. A Krokul app action: create a deal or a contact, with a contact search by phone or email before creating.
3. The native connection does the same without Zapier and adds the reverse direction, so Zapier fits when orders also have to go to other services.

**Triggers:** New Order; New User.

### For integrators

Deals from Horoshop start the same Krokul automations and webhooks as manual ones. The `card.created` and `card.statusChanged` events arrive signed with HMAC-SHA256 and with a delivery log. Items are matched through `externalRef` external keys, and a sandbox with demo data and a separate API key lets you test the setup.

[API documentation](https://app.krokul.com/api/v1/docs)

## Questions and answers

### Does Krokul have a Horoshop integration?

Yes, a native one. Krokul turns orders into deals with catalog items, syncs the order status both ways and sends stock and prices back to the store.

### Which way of connecting Horoshop should I choose?

On the Pro plan, webhooks deliver status changes, customer updates and comments at once. Krokul fetches new orders by polling the API, so they appear with a short delay. On other plans, polling covers everything.

### Will the old order history get into Krokul?

By default, no. The first pass only remembers the latest order. If you need the history, turn on «Import existing orders on the first pass».

### Is Horoshop available in Zapier?

Yes, with the New Order and New User triggers. You do not need it to connect Horoshop to Krokul, because the native connection receives orders directly.

## Limits

Horoshop offers webhooks on the Pro plan. On other plans, Krokul fetches orders by polling the API with a login and password, so an order arrives at the next pass. Horoshop runs the storefront, checkout and payment on the site, and Krokul runs the sale after the order.

## Related services

- [Rozetka](https://krokul.com/en/integrations/rozetka/index.md)
- [Prom.ua](https://krokul.com/en/integrations/prom-ua/index.md)
- [Nova Poshta](https://krokul.com/en/integrations/nova-poshta/index.md)
- [Checkbox](https://krokul.com/en/integrations/checkbox/index.md)
- [WooCommerce](https://krokul.com/en/integrations/woocommerce/index.md)
- [Shopify](https://krokul.com/en/integrations/shopify/index.md)

[Marketplaces and shops (Ukraine)](https://krokul.com/en/integrations/category/marketplaces-ua/index.md)

Horoshop is a trademark of its owner. Krokul is not affiliated with Horoshop.

Updated: 2026-10-15

---

App: https://app.krokul.com/ · API: https://app.krokul.com/api/v1/docs