Bitrix24 connector

TSync can connect to Bitrix24 so its CRM data can flow into your TSync platform — the second CRM connector alongside amoCRM. This first version sets up and tests the connection; importing leads and live sync arrive in the next versions.

Turn it on

A new connector ships deactivated and inert — it does nothing until you activate and enable it.

1. Go to Configuration Center → Module Management Center and activate the Bitrix24 module.
2. Open Integrations → Bitrix24 and click Enable connector (while it is off, no data is touched).

Add a connection

On Bitrix24 → Settings, click into the form and choose how to authenticate:

• Inbound webhook (simplest). In Bitrix24, create an inbound webhook (Developer resources → Other → Inbound webhook) with CRM access, and copy its URL (it looks like https://yourco.bitrix24.com/rest/1/abcd…/). Paste it into Inbound webhook URL. No app registration needed.
• OAuth 2.0 app. If you have a Bitrix24 local/marketplace app, enter the portal domain, client ID and client secret, then use Connect (OAuth). The redirect URI to register in your Bitrix24 app is shown on the form.

Type a name, fill the fields, and Save connection. Your credentials are encrypted before they are stored.

Test it

After saving, click Test connection. TSync calls Bitrix24 and shows whether it connected (and the profile name) or what went wrong. The connection's status and the time of the last test are kept on the list.

What's kept private

All secrets — the webhook URL and the OAuth client secret — are stored encrypted. The connection logs never contain your tokens or secrets in clear text.

Who can see it

The connector registers four permissions — view, create, edit and delete — under Bitrix24 in Setup → Roles. A staff member needs at least view for the menu entry to appear at all; saving a connection needs create/edit, and removing one needs delete.

The sidebar entry appears as soon as the module is active and the person has view — it does not wait for the connector to be switched on, so you can find the page in order to turn it on.

Reference data, and why there is nothing to refresh

The CRM mapping console reads your Bitrix24 deal categories (pipelines), deal stages, users and deal custom fields, so you can line them up with their TSync counterparts.

These are fetched live from Bitrix24 every time they are read — this connector keeps no local copy. So if you press Refresh reference data you are told there was nothing to bring up to date: you were already looking at the current values. Rename a stage in Bitrix24 and it is correct on your next page load.

The log

Bitrix24 → Logs records what the connector did — each connection test, each OAuth exchange, and each failure with the reason Bitrix24 gave. It is the first place to look when a connection that used to work stops working, because it separates "your credentials were rejected" from "Bitrix24 did not answer".

Tokens and secrets are never written to the log in clear text.

More than one company

If you run multi-company, every connection, token and log entry is anchored to the company it was created under. One company's Bitrix24 connection is not visible to, and cannot be used by, another.

What this connector does today

Plainly, because the section below has said "coming soon" for a while:

If you need to bring existing CRM records across today, amoCRM is the connector with a working importer.

What's next

This version is connection management + test. The upcoming versions add field/pipeline mapping, importing your Bitrix24 leads into TSync (matched so the same lead is never created twice), and keeping things in sync — the same way the amoCRM connector grew.