Use OAuth 2.0 tokens and API keys to securely authenticate Rankr requests to the GHL API.
Rankr uses API keys to authorize requests to GHL endpoints; ensure permissions.
The integration leverages a core set of endpoints for alerts, backups, users, and status information. A full endpoint map is available on request and is used based on the workflow.
Triggered by Acronis alerts; when a new threat or event is detected.
Create or update incidents in Rankr and push notifications to your security team.
Endpoint: /api/acronis/cp_cloud/alerts/sync
key fields: id, timestamp, status, severity, title, description
Scheduled via Rankr workflows and policy triggers.
Sync backup statuses to Rankr dashboards and update compliance views.
Endpoint: /api/acronis/cp_cloud/backups/sync
key fields: id, policyId, nextRun, status, lastRun
Triggered when a Rankr user is created or updated.
Create or update user accounts in ACRONIS and synchronize roles and permissions.
Endpoint: /api/acronis/cp_cloud/users/sync
key fields: userId, email, role, status, lastLogin
Fast setup with drag-and-drop automations.
Reduced manual work and fewer errors via integrated data flows.
Centralized visibility of protection events in Rankr dashboards.
This section defines important concepts: endpoints, triggers, actions, and data fields used in the integration.
A defined URL path through which Rankr communicates with the GHL API to perform a specific action.
An event from GHL or Acronis that initiates a workflow in Rankr.
The process of validating identity to securely access APIs.
A piece of information exchanged during the integration, such as id, status, or timestamp.
Route critical alerts from Acronis to Rankr dashboards and team chats for instant response.
Automatically verify protection policies in Acronis against Rankr workflows and flag drift.
Trigger remediation steps in ACRONIS directly from Rankr actions.
Generate API keys in Acronis, grant Rankr the required scopes, and verify connection.
Map Acronis endpoints to Rankr triggers and define actions.
Run tests, monitor logs, and enable production flow.
Yes. The connection uses OAuth2 and API keys with scoped permissions. Rankr handles token refresh automatically, and all data is transmitted over HTTPS with encryption at rest. Regular security reviews are performed.
Endpoint coverage includes alerts, backups, users, and status fields. You can request a complete endpoint map if needed, and we provide examples and payload schemas.
No extensive coding is required. We provide a guided setup and configurable triggers, with optional developer slots for advanced customization.
Yes. Triggers can be customized by mapping Rankr events to Acronis actions, including conditional logic.
Rankr dashboards show sync status, last updated times, and failure alerts. You can set notifications and alert rules.
Common data fields include id, subject, status, timestamp, and policy_id. Sensitive fields are secured and not exposed without authorization.
Yes. The no-code workflow designer allows you to build automation without coding, using visual triggers and actions.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
