Your GHL API access uses a scope of businesses.readonly and requires either an API key or OAuth 2.0 to authorize requests from Rankr.
To establish the connection, authorize Rankr within your GHL account and provide the necessary tokens or credentials. Use a secure method and test the connection.
GET /businesses; GET /businesses/:businessId; POST /businesses; PUT /businesses/:businessId; DELETE /businesses/:businessId.
Trigger: when a new business is created in GHL, create a corresponding record in Rankr.
Actions: create Rankr record, map id, name, and status to Rankr fields.
GET /businesses
Key fields: id, name, status
Trigger: when a GHL business is updated, push changes to Rankr.
Actions: update Rankr record fields to reflect the latest GHL data.
PUT /businesses/:businessId
Key fields: id, lastUpdated, name, address
Trigger: when a GHL business is deleted, archive or remove the Rankr entry.
Actions: delete or archive the Rankr record and scrub related mappings.
DELETE /businesses/:businessId
Key fields: id, status
Automate data flow without writing code, saving time and reducing errors.
Real-time syncing and centralized records for better decision making.
Prebuilt templates and mappings speed up setup and maintenance.
Understand core concepts: endpoints, triggers, actions, and data mapping that power the GHL to Rankr flow.
A set of rules and endpoints that allow two apps to talk to each other.
A specific URL with a method to perform an action, such as GET /businesses.
An event that starts a workflow or data sync.
Credentials or tokens used to verify identity and authorize requests.
Set up an automation to create a corresponding Rankr/Accelo entry whenever a GHL business is added or updated.
Run a weekly sync to reconcile records between GHL and Rankr and ensure Accelo data stays consistent.
Use retry rules and notifications if a map fails or an endpoint is temporarily unavailable.
Obtain your GHL API key and ensure the scope is set to businesses.readonly.
In Rankr, start a new GHL connection and complete the OAuth flow or paste the API token.
Define mappings for id, name, status and test the integration with a sample record.
The GHL Business API scope businesses.readonly grants read-only access to business records. This keeps your data secure while allowing Rankr to retrieve necessary details and reflect them in Accelo. If you need write access, upgrade the scope accordingly and adjust your permissions.
Authentication with Rankr is done via OAuth or API key. In most setups, you’ll authorize Rankr from within GHL and grant the necessary permissions. After approval, Rankr can start syncing data without exposing credentials in your workflows.
For a basic sync, use GET /businesses to pull data, and GET /businesses/:businessId to fetch details. Map essential fields like id, name, and status. You can extend with PUT and DELETE as needed.
Yes. Rankr provides field-mapping templates and you can customize mappings to fit your data model. Test mappings with sample data to ensure accuracy.
When a call fails, Rankr will retry according to your configuration. Set retries, backoff timing, and alerts to keep your team informed of persistent issues.
Yes, no-code options exist. Use the built-in connectors to authenticate and configure mappings without writing code.
View logs in Rankr under the GHL connection section. Test results show in the console and error details help diagnose problems.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
