Connectors
Import tasks and data from external tools into your Decuga project
How it works
Connectors let you pull existing tasks and issues from third-party tools (Jira, Bitrix24, and more) directly into a Decuga project, or push real-time notifications to external channels like Slack. Once connected, you trigger an import manually from the Settings → Integrations tab — or re-run it at any time to pick up new items.
Connect
Enter your credentials (API token or webhook URL) in the Integrations tab. Credentials are encrypted at rest.
Import
Click "Import now". The connector fetches items from the source and creates Decuga tasks. Already-imported items are skipped.
Configure
Use the Configure panel to adjust optional settings (project key, group filter, status filter) without reconnecting.
Available connectors
Jira
Import issues from Jira Cloud projects into Decuga tasks.
Required fields
Bitrix24
Import tasks from your Bitrix24 workspace using an inbound webhook.
Required fields
Slack
Receive Decuga notifications in any Slack channel. Task assignments, mentions, ticket updates, change approvals — all delivered in real time.
Required fields
Auth types
Decuga connectors use two authentication methods, depending on the source tool:
API Token (Jira)
You generate a personal API token in your Atlassian account settings and enter it together with your email and Jira domain. Decuga sends Authorization: Basic base64(email:token) on every API request. No partner registration required.
Inbound Webhook URL (Bitrix24)
Bitrix24 generates a REST endpoint URL that has the auth token embedded in the path (e.g. …/rest/1/abc123/). You paste this URL into Decuga. API calls append the method name to this base URL — no separate header needed.
Incoming Webhook URL (Slack)
Slack's Incoming Webhooks give you a dedicated https://hooks.slack.com/services/… URL that accepts POST requests with a JSON body. No OAuth partner registration is required — create the webhook in your Slack App settings and paste the URL into Decuga.
In all cases, your credentials are encrypted with AES-256-GCM before being stored.
Running imports
Imports run asynchronously. After clicking Import now, the connector fetches items in the background and reports progress in the Import history panel.
| Status | Meaning |
|---|---|
| Pending | Job queued, not yet started. |
| Running | Fetching items from the source. The panel polls every 3 seconds. |
| Completed | Import finished. Shows how many items were fetched, imported, and skipped. |
| Failed | An error occurred (auth failure, network timeout, etc.). See error summary for details. |
Re-running an import is safe — items already present in Decuga are detected by their external ID and skipped. Only new items from the source are created.