OLX is one of Ukraine's largest classifieds. The adapter accepts normalized leads from the OLX Partner API and creates CRM records, so requests don't get lost.
Lead capture
Lead import
A worker polls the OLX Partner API and posts leads to /leads/import.
Source olx
Each lead is tagged source=olx for channel analytics.
Connection test
OAuth client_credentials → users/me validates API access.
What becomes a lead
- The request name
- Email or phone of the contact
- The message text in notes
- Source: olx
- Duplicate protection via a stable external ID
Worker-push model
Polling the OLX Partner API and normalization stay in your worker; the CRM accepts ready leads through a secured endpoint. Leads are one-way — there is no reverse-sync.
Setup
- 1
Create an adapter secret
To secure /leads/import via X-Adapter-Secret.
- 2
Add OLX API credentials
The OLX Partner API client id and secret; test the connection.
- 3
Run a worker
The worker pulls requests from OLX and posts normalized leads to the CRM.
Frequently asked questions
Is it a two-way chat?
No — it's lead capture. A two-way OLX chat in the CRM is not part of v1.
Why store API credentials in the CRM?
So you can verify OLX Partner API access with a button; your worker uses the same credentials.
Stop losing OLX leads
Listing requests in your pipeline.
Start for free