Use casesUse case
Client memory for your GoHighLevel sub-accounts
A HighLevel agency can give each sub-account its own Context Engine engine and save contacts, appointments, form answers and deal moves to it with the Custom Webhook workflow action, so the agency's and the client's AI tools answer from everything that happened.
What it does
Everything an agency’s AI tools need to know about a client’s customers already passes through the sub-account: new contacts, booked and attended appointments, form answers, deals moving through the pipeline. It just never reaches the AI. With one engine per sub-account, a few HighLevel workflows save each of those events as a memory, and the agency’s Claude, ChatGPT, Cursor or n8n agents read that memory before they write, reply or report. The client’s team can open the same engine in the app and ask it questions.
Set it up for one sub-account
- In Context Engine, make an engine for the client. Write its purpose in a few sentences: “Everything we know about the client’s customers: contacts, calls, appointments and deals.”
- Make an engine key for it: AI tools → Connect an AI tool → Your own code → Another kind of key, an engine key that records things (or reads and saves). It is shown once.
- In the sub-account, save the key and the engine’s slug as custom values, for example
ce_engine_keyandce_engine. - Add a workflow per event (below). Each ends in a Custom Webhook action (a HighLevel premium action): method
POST, URLhttps://app.contextengine.com/tool/write, headersAuthorization: Bearer {{custom_values.ce_engine_key}}andContent-Type: application/json. - Connect your own AI tool to the engine with Connect an AI tool and ask: “What happened with this client’s customers this month?”
The workflows
| Trigger | Saves as | Title |
|---|---|---|
| Contact created | person | the contact’s name |
| Appointment Status (Showed) | meeting, with the time and attendees | appointment and contact name |
| Pipeline Stage Changed | note | deal name and new stage |
| Form submitted | note, with the answers | contact and form name |
A JSON body looks like {"engine": "{{custom_values.ce_engine}}", "type": "note", "title": "{{contact.name}} answered {{form.name}}", "body": "..."}. A meeting needs occurred_at and an attendees list in fields. Titles must be unique within an engine, so include a name or a date. Check the trigger and merge-field names in your own account, and test each webhook once before turning it on.
For agencies that want to offer this
Agencies that set Context Engine up for clients can join the partner programme and be listed in Find a partner.
Questions
Is there a Context Engine app in the HighLevel marketplace?
Not yet. The recipe on this page uses HighLevel's own Custom Webhook workflow action and a Context Engine engine key, (a HighLevel premium action), so it works in a sub-account today.
Does each client get its own memory?
Yes. One engine per sub-account. Every engine has its own database and search index, and each key or AI tool reaches only the engines you choose.
Can the client's own team see it?
Yes. Invite them to the engine; people are free on every plan, as admin, member or viewer.