Docs
Getting Started
From signup to your first script running on a GoHighLevel sub-account. ~10 minutes.
1. Sign up and create a workspace
Head to veloxscript.com/signup. One account controls one workspace — you can invite teammates later from Settings → Team. The free tier works for a single GHL sub-account; upgrade when you need more locations, scripts, or seats.
2. Connect GoHighLevel
Go to Settings → Integrations and click Connect GoHighLevel. You'll paste an agency-level Private Integration Token from GHL's Marketplace → My Integrations. We sync your sub-accounts on connect, and you can click Re-sync anytime you add new locations in GHL.
locations/readonly scope. We never store your GHL password or OAuth tokens — only the Private Integration Token, encrypted at rest.3. Generate an install token
Go to Settings → Install and click Generate token. Every request from your GHL pages carries this token — think of it as the workspace's API key. One token usually covers one agency; rotate if it ever leaks.
4. Paste the snippet into GHL
Copy the snippet from the Install tab — it's one line:
<script src="https://veloxscript.com/api/loader/wst_abc…xyz.js" async fetchpriority="high"></script>
In GoHighLevel, navigate to Settings → Company → Custom Code and paste the tag into the Custom JavaScriptfield. Save. That's it — the loader is live on every page of every sub-account under the agency.
.jsURL contains your install token. Don't share it publicly — treat it like an API key. It only authorizes reading the script bundle, not writing. Revoking and regenerating takes ~5 seconds.5. Create your first script
In the VeloxScript dashboard, click + New Script. Give it a title, pick JavaScript / CSS / Both, paste your code, and save. Scripts default to Live immediately.
Open the GHL page where you want to see it run and hit refresh. The script should inject within about 30 seconds (the loader bundle is edge-cached for freshness).
<script> block. The editor auto-strips wrapping <script> and <style> tags on save, but authoring clean source makes the history tab easier to read.6. Target specific sub-accounts
Open any script and switch to the Locations tab. By default, scripts run on every sub-account (all). Switch to selectedif the script should only run on certain locations — e.g. a logo swap that's specific to one client.