To begin, generate and securely store API keys or tokens from the GHL dashboard and apply the appropriate scope such as payments/coupons.readonly to access the endpoints you need.
In Gurucan, configure the app credentials and authorize connections using OAuth tokens or API keys provided by the platform, keeping tokens secure and rotated regularly.
The endpoints below cover payments, coupons, and products. Use the ones listed here and refer to additional endpoints if your integration requires them.
Trigger when a coupon is created or a payment occurs in Gurucan, then push updates to the store via the Coupons endpoints.
Actions include create or update coupons, verify payments, and apply discounts in real time.
Supported methods: GET, POST, PUT, DELETE for /payments/coupon and related coupon endpoints.
Key fields: code, amount, expiry, productId, status.
Trigger when products are added or updated in Gurucan to keep the catalog in sync with the API.
Actions include create, update, and delete product records; synchronize pricing and stock as needed.
Endpoints include GET /products/, GET /products/:productId, POST /products/, PUT /products/:productId, DELETE /products/:productId.
Key fields: productId, name, price, stock, sku, description.
Trigger stock level or price changes in Gurucan to update the store endpoints accordingly.
Actions include adjust inventory, update pricing, and notify stakeholders of changes.
Methods include PUT /products/:productId for updates and DEL /products/:productId for removals.
Key fields: productId, stock, price, sku.
Build powerful automations without writing code and connect Gurucan to your store in minutes.
Automate data flows between Gurucan and your store to reduce manual work and errors.
Access real-time data, dashboards, and alerts to stay on top of critical metrics.
Familiarize yourself with endpoints, triggers, actions, methods, and key fields used in the Gurucan to Products & Store API integration.
URLs that expose resources in the GHL API for payments, coupons, and products.
The process to verify identity and authorize requests via API keys or OAuth tokens.
Events that start automations when data changes in Gurucan or the GHL API.
Operations performed by the system in response to triggers, such as create, update, or delete.
Set up triggers to notify teams when coupon usage changes, enabling timely promotions.
Sync product data from Gurucan into your catalog to keep listings fresh and accurate.
Trigger restock reminders when stock falls below a defined threshold to prevent outages.
Generate and securely store your API keys in Gurucan and configure them in your GHL app credentials.
Assign necessary scopes such as payments.readonly and products.readonly, and map endpoints to your Gurucan workflows.
Test in a sandbox; verify data flows for coupons and products; then deploy to live environment.
The GHL API exposes resources used to manage payments, coupons, and products, while Gurucan data represents your course or store content. They share common RESTful patterns, but authentication and permissions are defined on the GHL side and mapped into Gurucan workflows. Use the shared endpoints to synchronize transactions and catalog changes.
No heavy coding is required. The integration is designed for no-code automation inside GHL workflows and Gurucan triggers. You can connect via API keys or OAuth tokens and build automation rules using built-in actions and conditions.
Endpoint availability depends on your plan and scope. Commonly used endpoints include payments/coupon, payments/coupon/list, and product endpoints such as /products/ and /products/:productId. Review your API plan for exact access.
Authenticate using securely stored API keys or OAuth tokens. Rotate credentials regularly, use least-privilege scopes, and utilize secure storage in Gurucan and GHL dashboards.
Yes. Webhook triggers can be customized to fire on specific events like coupon creation, product update, or stock changes. You can tailor payloads and routing in your automation workflows.
There can be rate limits per endpoint depending on your plan. Plan for retries with exponential backoff and cache data where appropriate to minimize repeated calls.
Use the Sandbox or Testing environment provided by GHL and Gurucan to validate endpoints before going live. Monitor request/response logs and verify data integrity.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
