Skip to content
Kotally Docs

Troubleshooting

Install did not activate

Section titled “Install did not activate”
  • Confirm the Marketplace OAuth approval completed for the intended sub-account.
  • Confirm workspace billing is active or trialing.
  • Check Admin -> Locations for a pending or disconnected location.
  • Reinstall from GoHighLevel only after confirming the existing install is not already linked.

API workspace not ready

Section titled “API workspace not ready”
  • Confirm billing is active or trialing (or the free trial is still valid) — a location cannot activate without it.
  • Create the API location from the setup modal (Use the API) or Admin → Locations → Add location (not from a Getting Started POST).
  • Confirm the location appears under Admin → Locations, then create a key under Admin → API Clients.
  • Copy the token immediately — it is shown only once.
  • Creating members requires the manage scope (POST /api/v2/contacts).

Purchase did not grant credits

Section titled “Purchase did not grant credits”
  • Confirm the GoHighLevel webhook reached /webhooks/ghl.
  • Confirm the payment event contains a GoHighLevel product id.
  • Confirm exactly one active product mapping exists for that product in the same location.
  • For invoice payments, confirm the invoice item product id maps to a Kotally product config.
  • If Stripe fallback is enabled, remember GoHighLevel-native grants are primary and duplicate commercial events are suppressed.

Booking did not deduct

Section titled “Booking did not deduct”
  • Confirm the contact has a Kotally entitlement for the appointment calendar.
  • Confirm the entitlement has credits remaining and is not expired or paused.
  • Confirm the appointment payload includes contactId and calendarId.
  • Check for SERVICE_FAMILY_MISMATCH when the customer has credits for a different calendar.

Embedded view is blank or missing context

Section titled “Embedded view is blank or missing context”
  • Confirm the user opened Kotally from a supported GoHighLevel surface.
  • Confirm the signed embed request reaches /embed/auth.
  • Use the Open Kotally fallback if the side panel cannot resolve contact context.
  • Ask support to inspect the location summary and recent events.

API request failed

Section titled “API request failed”
  • Use Authorization: Bearer <token>.
  • Confirm the API client has the required scope for the endpoint.
  • Confirm the token is allowed to access the requested location_id.
  • Reuse the same request_id only for an exact retry of the same operation.