HubSpot setup
Ticket Briefs without sending ticket text to ChatGPT or other third-party cloud LLM hosts. Inference runs on the gateway you host — on your hardware. Default is local. Other models, if any, are buyer-owned exits after local-only. Not a model marketplace. Policy or block filters on your gateway are a technical control, not legal cover.
Walkthrough (~4 min)
After purchase, watch Ping → Brief → Copy on a Help Desk ticket before you install.
Watch the NullTrace Router walkthrough (~4 min MP4).
What you need
- A HubSpot account where you can install apps
- A running NullTrace gateway (HTTPS) that you control
- A prepaid Standard ($49) or Pro ($299) pack from nulltracesystems.com (install is free; usage is prepaid)
1. Stand up your gateway
Customer-hosted. Run the NullTrace gateway and local model on hardware you control, expose a stable HTTPS origin, and keep that host awake.
The public HubSpot app can fetch only the lab origin HubSpot has allowlisted: https://gateway.nulltracesystems.com. That origin is a lab / demo gateway, not your production appliance.
If Briefs must hit your HTTPS hostname, you need a private HubSpot app build with that origin stamped for fetch. Typing a URL on the card does not bypass the allowlist. Email infrastructure@nulltracesystems.com with your exact HTTPS origin (scheme + host, no path, no wildcard) and HubSpot portal ID. We do not proxy ticket text through the lab gateway to fake customer-hosting.
2. Install the HubSpot app (OAuth)
- Open the NullTrace Router install link from your purchase email, marketplace listing, or NullTrace support.
- Choose the HubSpot account where tickets should get Brief.
- Approve the requested scopes:
tickets,oauth, andcrm.objects.contacts.read. - Finish the redirect. You should see a NullTrace confirmation that tokens were saved.
3. Find the card
Open a HubSpot ticket (Help Desk or CRM ticket record). In the right sidebar:
- Customize
- Card library
- Add NullTrace Router Brief
It lives on the ticket record, not under Settings → Record Customization. After it is added, complete first-run / portal mapping if prompted. Keep the tenant API key for your gateway; do not leave it in HubSpot client-side card settings. Gateway URL on the public app is the lab origin above; a custom customer origin requires the private build in step 1.
4. Ping, then Brief
- On the card, click Ping first. That checks the card can reach the gateway. Do not skip it.
- If Ping succeeds, click Brief on a real ticket. Usage is metered against your prepaid balance.
- Copy the suggested reply if you want it on the ticket. The card does not auto-publish.
5. Billing and keys
- Apps install free. Live prepaid packs: Standard $49 and Pro $299 on nulltracesystems.com. Trial ($0, once per portal) is requested by email. Business volume packs: email infrastructure@. Usage is Stripe metering (
nulltrace_tokens), not a HubSpot SKU. - Paid packs auto-mint on Fly after checkout. You may still need the key applied to your gateway
tenants.json— it is in the install email. Trial is minted after the email request (once per portal). - Manage billing in the Stripe Customer Portal link from your install email.
- Zero balance returns a clear paywall / 402-style path in the card instead of silent failure.
Data flow
- HubSpot → your gateway: ticket text and related fields needed to build a Brief (via the card / app).
- Your gateway → local model: inference on hardware you operate. Default is local. NullTrace does not fan ticket text out to ChatGPT or other third-party cloud LLM hosts.
- Your gateway → Stripe: metering events and billing metadata (not ticket bodies).
- Contacts read scope: used only when Brief needs contact context tied to the ticket; not for marketing sync.
Policy or block filters on the gateway are not a legal exemption. They do not let you send ticket text to any AI without counsel review. DPA and counsel review before regulated production use.
Support
Email infrastructure@nulltracesystems.com. Canonical setup URL: https://nulltracesystems.com/setup. Also see Privacy, Terms, and Refunds.