UptimeGuard × Bitrix24
Интеграция с Битрикс24
Create tasks, notify teams, and sync alerts with your CRM — all automatically when a monitored host goes down.
Availability monitoring for Russian IT teams
webhook-setup
Webhook Configuration
UptimeGuard sends HTTP POST payloads to your Bitrix24 inbound webhook URL the moment a check fails. No middleware, no polling — just a single JSON event delivered within 3 seconds of detection.
Generate an inbound webhook in Bitrix24 under Settings → Integrations → Webhooks, then paste the endpoint into UptimeGuard's integration panel. Each payload includes the monitor ID, hostname, last successful response time, current status code, and a timestamp in ISO 8601 format. All requests are signed with an HMAC-SHA256 header so Bitrix24 can verify the source before processing.
Endpoint Requirements
The webhook URL must accept POST requests with Content-Type: application/json. Bitrix24's built-in inbound webhooks handle this natively. UptimeGuard retries failed deliveries up to 3 times with exponential backoff (10s, 30s, 60s).
Payload Schema
Each event contains: monitor_id (UUID), host (FQDN or IP), status (down/degraded/recovered), last_ok_at (ISO timestamp), response_code, latency_ms, and region (e.g., MOW-1 for Moscow).
Security
Requests include an X-UptimeGuard-Signature header computed with your shared secret. Bitrix24 can validate this signature using a simple webhook script before triggering any automation rules or task creation.
task-creation
Automatic Task Creation
When a monitored host goes down, UptimeGuard creates a task in your Bitrix24 workspace assigned to the on-call engineer or the entire DevOps department — no manual triage required.
Tasks are created via the Bitrix24 REST API using your integration token. Each task includes a structured title (e.g., "[CRITICAL] api.example.ru — HTTP 502 since 03:14 MSK"), a description with the full incident timeline, and a priority level mapped from the monitor's alert rule. You can configure task templates per monitor so that DNS failures, SSL expiry warnings, and full outages each produce differently formatted tasks.
Assignment Rules
Map monitors to Bitrix24 users or departments. For example, DNS checks for mail.example.ru can auto-assign to the infrastructure team (department ID 12), while SSL certificate alerts for shop.example.ru route to the security lead (user ID 487). Round-robin assignment is supported for on-call rotations.
Recovery Auto-Close
When UptimeGuard detects that the host is back online, the corresponding Bitrix24 task is automatically marked as completed with a recovery comment. The comment includes downtime duration (e.g., "Resolved after 14 min 22 s") and the timestamp of the first successful check post-outage.
Task Templates
Define custom Markdown templates for task descriptions. Include dynamic fields like {{host}}, {{status_code}}, {{downtime_seconds}}, {{check_region}}, and {{monitor_url}}. Templates are stored in UptimeGuard and rendered server-side before the API call to Bitrix24.
crm-sync
CRM Sync for Sales Teams
Connect uptime alerts to Bitrix24 CRM so your sales managers are instantly notified when a client's hosted service experiences an outage — enabling proactive communication before the client even calls.
UptimeGuard maps monitored hosts to Bitrix24 CRM deals or company records. When a check fails, a CRM activity (task or call reminder) is created on the linked deal with a note about the incident. For example, if cdn.client-portal.ru goes down and that host is linked to deal #28491 ("Q3 hosting renewal — OOO VectorNet"), the account manager receives a task: "Client outage detected — reach out to OOO VectorNet" with the incident details.
Deal Linking
Associate each monitor with a CRM deal by deal ID or by matching the hostname to a field in the company card. UptimeGuard stores this mapping and uses it to route alerts to the correct account owner. Bulk import is supported via CSV with columns: monitor_id, deal_id, manager_id.
Manager Notifications
Sales managers receive Bitrix24 portal notifications and optional Telegram or email alerts when a linked host goes down. The notification includes the client name, service affected, estimated impact, and a direct link to the UptimeGuard incident page so they can share status updates with the client.
SLA Reporting
Monthly uptime reports are pushed to Bitrix24 as CRM documents attached to the relevant deals. Each report shows availability percentage per host, total downtime minutes, and MTTR. Managers can reference these reports during renewal negotiations — for example, showing OOO VectorNet that their services maintained 99.94% uptime across all 7 monitored endpoints in October 2024.
getting-started
Start in Under 5 Minutes
Connect UptimeGuard to your Bitrix24 portal, configure your first webhook, and have automated tasks running before your next standup.
1. Create a Bitrix24 Webhook
Go to Settings → Integrations → Webhooks in your Bitrix24 portal. Create an inbound webhook and copy the URL. No additional permissions are needed beyond standard task and CRM access.
2. Paste into UptimeGuard
Open your UptimeGuard dashboard, navigate to Integrations → Bitrix24, and paste the webhook URL. Enter your shared secret and select which monitors should trigger events. Save and test with a dry-run payload.
3. Verify and Go Live
UptimeGuard sends a test event immediately. Confirm that a task appears in your Bitrix24 workspace. Once verified, the integration processes all real-time alerts automatically. You can manage active integrations and review delivery logs from the UptimeGuard dashboard.