Social media API layer for your CRM
Socialift is the integration layer between a CRM and social networks: a Python SDK plus a web dashboard for the Instagram, Facebook, LinkedIn, TikTok and Telegram APIs. Your backend calls the SDK to read conversations, leads and comments, verifies platform webhooks with its helpers and writes the data through your CRM's API — instead of building each integration from scratch.
Updated:
What is a social integration layer?
An integration layer is software that sits between a CRM and external platforms. It hides each network's own API, authentication, limits and event format, and gives the CRM one stable stream of data. Your CRM team never has to learn the details of the Meta Graph API.
Wiring each platform separately is expensive: each has its own way to connect, its own error model, its own rate-limit policy and documentation that keeps moving. The layer concentrates that complexity in one place.
On the CRM side one job remains — mapping events onto your own objects: who owns the conversation, which pipeline the lead enters, whether a comment creates a task.
What the layer takes care of
One way to connect
The same pattern on every client — login_url() → exchange_code() → TokenBundle (access_token, expires_in, refresh_token). Telegram connects by phone code or BotFather token. Token lifetimes and revocation differ per platform.
Normalised Meta events
parse_events() turns Instagram and Facebook webhooks (messages, comments, leadgen) into one WebhookEvent shape; TikTok has parse_tiktok_event(), Telegram updates stay in Bot API format.
A stable contract
One method signature per operation; platform API version upgrades ship as SDK releases, and graph_version= / api_version= let you pin or move ahead yourself.
Webhook safety helpers
verify_request / verify_tiktok_request / verify_telegram_request check incoming signatures, dedupe_key() gives a stable key, RetryPolicy retries API calls on 429/5xx. Storage and queues stay in your backend.
Observability
The dashboard shows request and error counts, SDK and Playground/API calls separately, daily trends and the most-used endpoints.
Three languages
Documentation and support in Uzbek, Russian and English.
What each channel provides
| Channel | Conversations | Leads | Content | Webhooks |
|---|---|---|---|---|
| yesDirect | yesLead Ads | yesposts, carousels, comments | yes | |
| no | yesLead Ads | yesposts, comments | yes | |
| no | no | yesposts | no | |
| TikTok | no | no | yesvideo, photo carousels, comments | yes |
| Telegram | yesaccount and bot | no | yeschannel and group messages | yesbot |
yesnoScroll the table sideways
Notes and limits
The table shows what Socialift supports today. TikTok comments require a Business account. LinkedIn's Messages API and Lead Sync API are available only to approved partners, so Socialift does not offer them.
How to connect it to a CRM
Pick your channels
Start with the channel that brings the most enquiries — often that is Instagram Direct and Lead Ads.
Prepare the app and permissions
Keep the permission list minimal for the channels you chose; it makes App Review easier. You can add your own Meta, LinkedIn, TikTok or Telegram app keys on the “Kalitlar” (Keys) page of the dashboard: they are encrypted and verified with the provider in one click.
Get a token and install the SDK
Sign in with Google, take the slk_ key and run pip install socialift.
Write the webhook receiver
Verify the signature, return 200, and push processing onto a queue.
Map events onto CRM objects
Conversation → contact and deal, lead → lead, comment → task. This step is where the value lives.
Set your KPIs
First response time, lead volume and conversion by source — measure the integration by those.
Frequently asked questions
Is Socialift a CRM or an add-on for one?
Socialift is not a CRM. It is an integration layer: your backend uses its Python SDK to read data from social networks and writes it into your CRM. Deals, tasks and reporting stay in your CRM.
Are there plugins for off-the-shelf CRMs?
No. There are no ready connectors for amoCRM, Bitrix24 or other CRMs. Your backend reads data with the Python SDK and writes it through your CRM's API, so any CRM with an API works.
Could I build an omnichannel inbox myself?
Yes, and sometimes that is the right call. A layer earns its place when several platforms are involved, APIs change often and delivery reliability matters.
Where is the data stored?
Tokens of accounts connected in the dashboard on the “Ulanishlar” (Connections) page are stored encrypted on the server and never sent to the browser. The Python SDK stores nothing: tokens and data live in your own database. Details are in the privacy policy.