Integrations
Bitrix24
Connect Bitrix24, obtain the required access and configure permitted actions.
The API adapter is implemented. Validate your own account and authorized actions before routing production calls.
Before you start
Connect the account belonging to this business and workspace. Vendor subscriptions, API limits and role permissions still apply.
API: Bitrix24 REST API, universal CRM item methods, activities and timeline comments
Authentication: Customer-managed Bitrix24 OAuth app with client ID, client secret and rotating refresh token
Get access and connect
- Use a Bitrix24 cloud portal with REST access. Register a local OAuth application in the portal's developer resources or a distributable application through https://www.bitrix24.com/apps/dev.php; configure a server-side authorization callback.
- Complete Bitrix24's OAuth authorization flow and retain the application's client ID, client secret, access token and refresh token. The app must request the crm and user scopes needed by these actions.
- Enter the portal's root HTTPS origin in Verbatik, for example https://your-company.bitrix24.com. Enter clientId, clientSecret and refreshToken in the encrypted credential fields. The access token is optional when the renewal configuration is complete.
- Verbatik renews credentials at the fixed official oauth.bitrix.info endpoint, verifies the returned portal endpoint when present, and persists the new token pair. The portal REST methods receive OAuth auth as an authentication parameter.
- Run Test connection (user.current). Use Read CRM fields before configuring record writes so camelCase universal CRM fields and known stage IDs match the portal.
- Configure CRM follow-ups with the current universal activity API. Call logging uses the still-documented legacy system-call activity method because it represents a completed phone interaction; it never places a phone call.
Account requirements
- The portal plan must permit REST API use and the authorizing employee must have CRM record/activity permissions. Local app creation and installation require the applicable portal administrator/developer permissions.
- Access tokens last one hour; refresh tokens last 180 days and rotate. Store the full renewal configuration for unattended use. A manually pasted access token alone is temporary.
- The adapter accepts reviewed Bitrix24 cloud portal domains and does not accept arbitrary on-premise Bitrix hosts or incoming-webhook URLs as OAuth credentials.
- Existing pipeline/stage fields and required portal custom fields apply. CRM API errors may arrive in JSON envelopes and are checked before confirming a completed action.
Permissions
crmuser
Grant the subset needed for the actions you enable. API scopes do not override the connected user’s record permissions or vendor validation rules.
Connection fields
accessToken— Bitrix24 access token (optional with automatic renewal) (optional). Secret fields are saved as workspace credentials.clientId— OAuth client ID (automatic renewal) (optional). Secret fields are saved as workspace credentials.clientSecret— OAuth client secret (automatic renewal) (optional). Secret fields are saved as workspace credentials.refreshToken— OAuth refresh token (automatic renewal) (optional). Secret fields are saved as workspace credentials.instanceUrl— Bitrix24 cloud portal origin (required).
Available actions
test_connection— Read · available for after-call automation. Read account or schema metadata to verify credentials without creating records.list_records— Read · available for after-call automation. Filter supported CRM records using documented universal CRM field names.get_record— Read · available for after-call automation. Read a supported universal CRM item.get_fields— Read · available for after-call automation. Read available CRM item fields before creating or updating a record.create_record— Write · available for after-call automation. Create a lead, deal, contact or company using universal CRM field names.update_record— Write · available for after-call automation. Update a supported CRM record or move its stage using a known stageId.add_note— Write · available for after-call automation. Add a timeline comment to a known CRM record.create_task— Write · available for after-call automation. Create a universal follow-up activity on a CRM record.log_call— Write · available for after-call automation. Record a completed system-call activity related to a known CRM record and contact. Does not place a call.
Verify before going live
Run Test connection and one read action against a known permitted record. Then test each intended write in an authorized sandbox. Check the provider’s own record and the Verbatik receipt. Publish the agent after assigning its tools. If a write has an unknown outcome, reconcile it with the vendor before trying again.