🟠

Bitrix24

Import tasks from your Bitrix24 workspace into Decuga

Inbound webhook auth

No OAuth required

Cloud & On-premise

Overview

No OAuth app registration or partner account needed. Authentication uses a Bitrix24 inbound webhook URL that you generate inside your Bitrix24 portal in under a minute.

The Bitrix24 connector imports tasks from your Bitrix24 workspace into Decuga. It authenticates via an inbound webhook URL — a REST endpoint generated by Bitrix24 that contains an authentication token directly in the URL path.

A typical inbound webhook URL looks like:

url

https://mycompany.bitrix24.com/rest/1/abc123xyz456/

Decuga appends REST method names to this base URL to call the Bitrix24 API — no separate auth headers or OAuth tokens needed.

Setup

Open the inbound webhook settings in Bitrix24

navigation

Left menu → Applications → Developer resources → Other → Inbound webhook

Or go directly to:

url

https://your-domain.bitrix24.com/devops/section/inbound_webhook/

You need administrator access or the Developer tools permission to create webhooks. Ask your Bitrix24 administrator if you do not see the Applications menu.

Configure webhook permissions

On the inbound webhook creation page, enable the following scope:

Scope	Why it is needed
task	Read access to Bitrix24 tasks

Leave all other scopes disabled unless needed for other purposes.

Save and copy the webhook URL

Click Save. Bitrix24 will display your new inbound webhook URL, for example:

url

https://mycompany.bitrix24.com/rest/1/a1b2c3d4e5f6g7h8/

Copy this URL now — the token embedded in the URL path is your credential. If you lose it, regenerate a new webhook in Bitrix24 and reconnect in Decuga.

Find your Group ID (optional)

Bitrix24 organises tasks into Groups (also called Projects or Workgroups). To limit imports to a specific group, find its numeric ID:

Go to Tasks → Projects in your Bitrix24 portal.
Open the group you want to import from.
The URL will contain the ID: …/workgroups/42/tasks/

Leave blank to import tasks from all groups your account has access to.

Connect Bitrix24 in Decuga

In your Decuga project, go to Settings → Integrations and click Connect on the Bitrix24 card. Fill in the form:

Field	Description
Inbound Webhook URL	The full URL copied in step 3, including the trailing slash
Group / Project ID (optional)	Numeric ID of the Bitrix24 group to import from

Click Connect to save the integration.

Run your first import

Once connected, click Import now on the Bitrix24 card. Imports run asynchronously — expand Import history to monitor progress. Re-running an import skips tasks already present (matched by Bitrix24 task ID).

Field mapping

Bitrix24 task fields are mapped to Decuga task fields as follows:

Bitrix24 field	Decuga field
TITLE	Title
DESCRIPTION	Description
STATUS (3=in progress, 4=done)	Status — To Do / In Progress / Done
PRIORITY (0=low, 1=medium, 2=high)	Priority
DEADLINE	Due date (date part only)
ID	External ID (stored in custom fields)

Troubleshooting

Authentication failed (HTTP 401 or 403)

The webhook URL may be incorrect or the token may have been regenerated in Bitrix24. Copy the URL again from the Bitrix24 webhook settings and reconnect the integration in Decuga.

No tasks imported

The account that created the webhook may not have access to tasks in the specified group. Try leaving Group ID blank to import all accessible tasks.

"result" field is null in the response

This can happen if the "task" scope was not enabled when creating the webhook. Delete the webhook in Bitrix24, create a new one with the task scope enabled, and reconnect.

How do I rotate the webhook token?

Go to Bitrix24 → Applications → Developer resources → Inbound webhook, find your webhook, and click Regenerate. Copy the new URL and reconnect the integration in Decuga (Settings → Integrations → Reconnect).

Previous: Jira Next: Slack →