Prom.ua is one of the largest marketplaces in Ukraine. The integration is two-way: orders are imported into the CRM as crm_orders, and when a manager changes the status, the CRM sends it back to Prom.
Two-way flow
Order import
A worker polls the Prom Public API and posts normalized orders to /orders/import.
Status reverse-sync
A CRM status change → set_status on Prom (fire-and-forget).
Idempotency
A repeated externalId creates no duplicate; a typed conflict on mismatch.
Workspace isolation
Every order is tied to your workspace via the adapter token.
Prom → CRM field mapping
Setup
- 01
Create an adapter secret
Any secret as the key; the same value is sent in X-Adapter-Secret.
- 02
Run a polling worker
The worker fetches Prom orders on a schedule and normalizes them.
- 03
Add the status API token
Paste the Prom API token in the reverse-sync block and test the connection.
Frequently asked questions
Are duplicates stored?
No — import is idempotent on externalId; a repeated payload returns the existing order.
How does reverse-sync work?
After a CRM status change we call set_status on Prom in the background; the local status update never fails because of a sync error.
Connect Prom.ua
Marketplace orders in a single sales pipeline.
Start for free