Connect with OAuth 2.0 using your GHL API credentials and request the scope payments/coupons.readonly for viewing coupons. Upgrade to write access as needed for your workflow.
Authorize the Act! app to access your GHL data by linking the two apps in the developer portal and granting the required endpoints and scopes.
The integration can use these core endpoints: GET /payments/coupon, GET /payments/coupon/list, POST /payments/coupon, PUT /payments/coupon, DEL /payments/coupon, GET /products/, GET /products/:productId, POST /products/, PUT /products/:productId, DELETE /products/:productId. Additional endpoints may be available as needed.
Trigger: when a coupon is created or updated in Act! it is reflected in the Products and Store API
Actions: create, update, and delete coupons in the Products and Store API from Act! events
Method path: use GET /payments/coupon to fetch, GET /payments/coupon/list for lists; use POST /payments/coupon, PUT /payments/coupon, and DEL /payments/coupon to modify
Key fields: coupon_id, code, amount, expiration, status
Trigger: when a product is created or updated in Act! it is synced to the Products and Store API
Actions: create, update, or delete products using POST, PUT, and DELETE on /products
Method path: GET /products/ to list, GET /products/:productId to fetch, POST /products to create, PUT /products/:productId to update, DELETE /products/:productId to delete
Key fields: productId, sku, name, price, stock
Trigger: when an order is paid in Act! it updates coupons or payment records in the Products and Store API
Actions: create or update coupons and record payments via the Payments endpoints
Method path: use GET /payments/coupon for retrieval and POST /payments/coupon for creating payments or updates as needed
Key fields: payment_id, coupon_id, amount, currency
Automate coupon and product workflows without writing code
Centralized data flow between Act! and the GHL API for accuracy and speed
Faster time to market with ready to use endpoints and templates
Understand the building blocks: endpoints, authentication, triggers, actions, and data fields that move between Act! and the Products & Store API.
OAuth 2.0 is the standard framework used to grant secure access to APIs without sharing user credentials.
An API endpoint is a specific URL and HTTP method used to perform a defined action on a resource.
A discount code that can be applied to a purchase to reduce price or offer other promotions.
An item in the catalog that can be sold, with attributes such as name, price, and stock.
Automate discount campaigns by pushing Act! coupons to the GHL API and applying them at checkout.
Trigger personalized product suggestions in Act! based on inventory and pricing from the API.
Set up stock level alerts in Act! that push updates to the store catalog via the API.
In the GHL developer portal, create an OAuth client and capture the client ID and secret for the connection.
Request the appropriate scopes such as payments/coupons.readonly and upgrade as needed for write access.
Link Act! to the GHL connection in the app, authorize, and run test triggers to validate the workflow.
You will typically authenticate using OAuth 2.0 with a client ID and secret from your GHL developer account. The scope payments/coupons.readonly provides read access to coupons. For write operations you can request a higher scope such as payments/coupons.write. After authorization, you will configure the connection in Act! and select the endpoints you want to use. The setup is designed to be secure and frictionless for non developers.
No code options are available. This integration is designed to work with tools like Zapier that let you map triggers, actions, and data fields without touching code. You can enable or disable endpoints as needed and test each step in a staging environment.
The primary endpoints include coupon related endpoints under /payments/coupon and product endpoints under /products. You can retrieve, create and update coupons and products using GET, POST, PUT, and DELETE methods as needed for your workflow.
Yes. Coupons and products can be created, updated, or deleted from Act! using the GHL API endpoints. Ensure the proper scopes are granted and that you map fields correctly between systems.
Field mapping is handled in the integration builder. You can align product IDs, names, prices, and coupon codes between Act! and the GHL API to ensure data accuracy.
Yes. No code workflow builders let you create triggers, actions, and filters with a few clicks. Test in a sandbox environment before going live.
Deployment time varies with your data and complexity. A simple connection can be live within minutes, while a more complex setup may take a few hours to map fields and test end-to-end.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
