Settings

Connection, scopes and menu link for your sub-account.

Beta mode
Beta mode is on. The hub is locked to a single sub-account for testing. The API key is passed in automatically from the CRM menu link. Flip BETA_MODE to false in src/lib/beta-config.ts to move to the multi-location production model.
Sub-account connection
The hub operates on this location. The API key is supplied by the CRM menu link.
Demo

Location name

—

Location ID

tCNxX6SoDC8tUu9ybXwZ

API key

Not detected

No API key detected — open the hub from the CRM menu link to pass one automatically.
Required API scopes
Enable these in your sub-account's private integration key.
  • contacts.readonly
  • contacts.write
  • opportunities.readonly
  • objects/schema.readonly
  • objects/record.readonly
  • objects/record.write
  • associations.readonly
  • associations.write
  • associations/relation.readonly
  • associations/relation.write
  • locations/customFields.readonly
Objects linked to weddings
Custom objects and their opportunity associations. Link an object to weddings to use it on the wedding page.

Loading objects…

Custom menu link
Add this as a custom menu item in your sub-account.

In beta mode no parameters are needed — the location is pinned server-side. The API key is passed through the link fragment and stripped from the address bar on load. Point the menu item at your app root.

https://[your-published-domain]/#key={{custom_values.ghl_api_integration}}

For production (multiple sub-accounts), set BETA_MODE = false and switch to the ?location_id={{location.id}} form shown below.

Production link format — reads the sub-account from the URL:

https://[your-published-domain]/?location_id={{location.id}}#key={{custom_values.ghl_api_integration}}

Replace [your-published-domain] with your published app URL. Label the menu item "Vendor Hub".