Connect by authenticating with your GHL credentials and granting the payments/integration.readonly scope to securely access order data.
Ensure Rankr is authorized to call the GHL Orders API via API keys or OAuth, depending on your setup.
Included endpoints: GET /payments/integrations/provider/whitelabel; POST /payments/integrations/provider/whitelabel; GET /payments/orders/; GET /payments/orders/:orderId; GET /payments/orders/:orderId/fulfillments; POST /payments/orders/:orderId/fulfillments; GET /payments/transactions/; GET /payments/transactions/:transactionId; GET /payments/subscriptions/; GET /payments/subscriptions/:subscriptionId. (More endpoints may exist depending on your GHL plan.)
Trigger when a new order is created in Rankr to push or update the corresponding order in GHL.
Actions: create or update orders in GHL; pull fulfillment records.
POST /payments/orders/:orderId/fulfillments
orderId, status, totalAmount, currency, customerId
Trigger on transaction updates to keep Rankr orders aligned with payment data in GHL.
Actions: read transactions and map to orders.
GET /payments/transactions/
transactionId, orderId, amount, status
Trigger on subscription changes to reflect updates in GHL and Rankr.
Actions: read subscriptions and link to related orders.
GET /payments/subscriptions/:subscriptionId
subscriptionId, status, planId, amount
Automates data flow between Rankr and GHL, reducing manual entry.
Unifies payments, orders, fulfillments, and Trustpilot triggers in a single view.
Speeds up Trustpilot review collection by triggering requests after key order events.
This glossary covers GHL, Orders API endpoints, triggers, actions, and fields used in the Rankr integration.
GHL is the API integration platform used to connect Rankr with external services.
An order is a record of a purchase processed through Rankr.
Fulfillment tracks the delivery or completion status of an order.
A transaction is a single payment event processed via the Payments API.
Pull Trustpilot review scores alongside order data to tailor follow-ups.
Trigger Trustpilot review requests after fulfillment to boost response rates.
Notify teams when new reviews are posted that relate to recent orders.
Collect API keys and OAuth credentials from GHL.
Set the payments/integration.readonly scope to enable read access.
Run test calls to verify data flow and mappings.
You’ll typically use API keys or OAuth credentials from GHL to authorize Rankr. Ensure the credentials are stored securely and that the connection uses the payments/integration.readonly scope to access orders and related data. Always follow your security policies for credential management.\nIn practice, test the connection with a small data sample to confirm endpoints return expected data and that mappings align with your Rankr data model.
The core endpoints include: GET /payments/orders/ and GET /payments/orders/:orderId for orders; GET /payments/orders/:orderId/fulfillments for status updates; GET /payments/transactions/ and GET /payments/transactions/:transactionId for payments; GET /payments/subscriptions/ and GET /payments/subscriptions/:subscriptionId for recurring payments.\nUse these to synchronize data fields such as orderId, fulfillmentStatus, transactionAmount, and subscriptionStatus.
Read access (readonly) is often sufficient for reporting and dashboards. If you need to modify orders or create fulfillments programmatically, you’ll require write permissions (e.g., POST or PUT endpoints). Review your plan and security requirements before enabling writes.\nAlways follow the principle of least privilege and rotate credentials regularly.
Start with a sandbox or staging environment to run end-to-end tests of auth, endpoint calls, and data mappings. Verify data latency, error handling, and field mappings. Once the sample data matches your expectations, transition to production with caution and monitor closely.
The integration can sync orders, fulfillments, transactions, and subscriptions, plus basic customer identifiers. The exact data elements depend on the endpoints enabled in your GHL/Rankr setup, but typical fields include orderId, orderStatus, fulfillmentStatus, amount, currency, customerId, and subscriptionId.
Yes. Many integrations allow you to map fields and set sync frequency. You can select which fields to pull from each endpoint and determine how often you poll or push data, depending on your needs and API limits.
Trustpilot data enhances customer sentiment and review workflows. After an order is fulfilled or a payment is processed, you can trigger Trustpilot review requests or pull reviews to enrich customer profiles. This creates a closed loop between purchases, support, and social proof.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
