To authenticate with the GHL Connector API, generate an API key in the GHL developer console and include it in the Authorization header as a Bearer token. Use the appropriate scopes (read, write, and manage) for your integration and rotate keys regularly.
Access to Acronis Cyber Protect Cloud endpoints requires an API token or OAuth credentials. Create a service account in the Acronis console, grant necessary permissions, and store credentials securely with regular rotation.
Common endpoints used in this integration include: GET /devices to fetch inventory, POST /backup-plans to create or update plans, POST /backups/start to trigger backups, GET /jobs to monitor backup status, GET /alerts to pull security alerts, POST /policies to create policies, GET /policies to list them, GET /customers for account data, GET /organizations for tenant details, POST /webhooks to receive events, and GET /status to check system health. This is a representative subset; the full 54-endpoint catalog is available in the official docs and may be consulted as needed for your deployment.
Trigger: When a new device is added in GHL, automatically provision a corresponding backup plan in Acronis.
Actions: Create or update backup policies, attach schedules, and log activity back to GHL for traceability.
Method Path: POST /devices/sync
Key fields: device_id, plan_id, tenant_id
Trigger: Daily sync at 02:00 local time to align policies between GHL and Acronis.
Actions: Update or create backup policies, initiate batch backups, and push results to GHL.
Method Path: POST /policies/sync
Key fields: policy_id, device_group_id, last_sync
Trigger: When GHL raises a critical alert, push a remediation task to Acronis to isolate or remediate.
Actions: Create remediation task in Acronis, update alert status in GHL, and notify stakeholders.
Method Path: POST /alerts/remediation
Key fields: alert_id, remediation_id, resource_id
No-code integration lets you connect GHL with Acronis using visual workflow builders—no custom coding required.
Rapid deployment and iteration enable teams to test security and backup automation in days, not weeks.
Centralized monitoring and logging provide a single source of truth for protection workflows.
This glossary defines essential terms and outlines the end-to-end flow for the GHL–Acronis integration, helping teams understand data movement, events, and actions.
The RESTful API exposed by the GHL platform to access data and perform actions programmatically.
An authorization framework used to obtain access tokens for secure API calls.
A secret token used to authenticate requests to the GHL API.
A defined set of backup rules and schedules applied to a device or group of devices within Acronis Cyber Protect Cloud.
Build a single pane of glass in GHL that aggregates Acronis backup and remediation actions alongside security alerts for faster decision making.
Generate weekly reports combining GHL alerts with Acronis backup results and deliver them to stakeholders via Slack or email.
Provide pre-built templates for common workflows (e.g., ransomware response) to reduce time-to-value for teams.
Generate API keys for the GHL Connector API and create a service account in Acronis. Record client IDs, secrets, and tokens in a secure vault.
Identify the fields and endpoints needed for core flows (devices, policies, backups). Create mappings to ensure data consistency between systems.
Run test transactions, verify event triggers, and set up webhooks or notifications for failures. Monitor the integration in the first 14 days.
The GHL Connector API provides programmatic access to GHL data and actions, enabling you to connect external services like Acronis Cyber Protect Cloud. This integration allows you to automate backup, alerting, and remediation workflows without custom coding. You control which events trigger which actions across platforms.
No code is required for building basic connections using the Developer Marketplace templates and visual workflow builders. For advanced requirements, you can extend with lightweight scripts or custom endpoints, but many use-cases are satisfied with built-in automations.
Supported authentication includes API keys (Bearer tokens) and OAuth 2.0 tokens. Choose the method based on your security posture and the sensitivity of the data being accessed. Rotate credentials regularly and store them securely.
Yes. You can map fields and endpoints to suit your data models. The integration supports custom field mappings for devices, policies, and backup jobs, allowing you to align data formats between GHL and Acronis.
Monitor the integration via logs, dashboards, and webhook notifications. Set up alerts for failures or slow responses, and review a centralized activity stream to keep teams informed.
If a backup fails during a remediation workflow, the system can retry, escalate to a human operator, or trigger a fallback plan in Acronis. Alerts will reflect the remediation status in GHL for visibility.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
