Automation of exporting deals from CRM Bitrix24 to Google Sheets

1. Project Goal

Create an automated process for transferring transaction data from CRM Bitrix24 to Google Sheets.

The table should update in a near real-time mode and match the structure provided in the example.

2. Logic of Operation

• When creating a new deal → a new row with data from all fields is added to Google Sheets.

• When modifying a deal → the row in Google Sheets is found by the unique deal_id and updated.

• Creating duplicates is not allowed.

3. Integration Systems

• Source: Bitrix24 CRM (cloud version UK)

• Receiver: Google Sheets

4. Triggers

The integration should trigger when:

• a new deal is created;

• any fields of the deal specified in the mapping are changed.

5. Mapping

• All key fields from Bitrix24 should be exported to the corresponding columns in Google Sheets.

• If fields are missing in the CRM → the executor must create them.

• Important example: field Days to Purchase (calculated field).

(Table structures + link to Google Sheet provided)

6. Implementation Requirements

• Method of implementation:

  At the executor's choice — Bitrix24 webhooks + Google Apps Script / Make / Albato / Zapier / Python + API.

  The main condition is stability and optimal price/reliability ratio.

• Performance:

  The solution should not overload the Bitrix24 portal. Consider API limits (2 requests/second for the tariff).

• Reliability:

  
  

  • Error logging.

  • In case of failure → notification to email with deal ID and error description.

  • Exclusion of duplicates.

7. Work Results

The executor must provide:

1. A fully functional automation.

2. Access to the source code or script (if through no-code).

3. A brief instruction (how to use and what to do in case of failures).

4. A demonstration of the operation on 3–5 test deals.

10. Acceptance Criteria

The work is considered completed if:

1. 5 test deals are created and appear in Google Sheets within 2–3 minutes.

2. Changes to the deal data (amount, project type, purchase date, etc.) are reflected in the table within 2–3 minutes.

3. All fields from the mapping are exported correctly.

4. The executor demonstrated the operation of the error handling mechanism.