Activity
Mon
Wed
Fri
Sun
May
Jun
Jul
Aug
Sep
Oct
Nov
Dec
Jan
Feb
Mar
Apr
What is this?
Less
More

Owned by Dylan

theFurnace.ai

25 members • Free

Let Us Cook.

Memberships

Clief Notes

17.2k members • Free

Pinnacle Life Group

1.1k members • Free

Pinnacle Nation

103 members • Free

Assistable.ai

3.4k members • Free

High Ticket Insurance AI

636 members • Free

Skoolers

192.1k members • Free

13 contributions to Assistable.ai
Custom Values
Is it possible to use custom values in knowledge base?
0 likes • 5d
+1
Update Assistant API endpoint returns success but doesn't apply changes
@Jorden Williams @Mike Copeland , hoping you can help with an API issue we're running into. We're using the REST API to manage assistants across multiple GHL subaccounts. The PUT update-assistant endpoint consistently returns {"status": "success"} but the changes never actually apply. What we tested: - Updating prompt field - returns success, GET confirms no change - Updating name field - same result - Updating instructions field (in case the field name differed) - same result - Tested on 2026-03-25 and again today (2026-03-31), same behavior both times What works fine: - create-assistant (POST) - works, prompt and model are set correctly at creation - get-assistant (GET) - works, returns full assistant data - Auth is valid (wouldn't get 200 responses otherwise) Our setup: - Bearer token auth - Hitting https://api.assistable.ai/v2/update-assistant - Sending assistant_id, location_id, and the field to update - Response is always {"status": "success", "id": "..."} Example request: curl -X PUT https://api.assistable.ai/v2/update-assistant \ -H "Authorization: Bearer <token>" \ -H "Content-Type: application/json" \ -d '{"assistant_id": "<id>", "location_id": "<loc>", "prompt": "new prompt text"}' Why this matters for us: We run the same bot (CHLOE) across 9+ subaccounts. Right now every prompt update has to be done manually in the UI for each one. A working update endpoint would let us push changes to all subaccounts in one script. Is this a known issue? Is there a different approach we should be using, or a fix in the pipeline?
0
0
Multiple GHL Agencies
If I'm connected to multiple Go High Level agencies, is it best practice to create separate workspaces for each agency so that I can have the agency connection? I've seen some bugs where if I do a direct connection with one agency and then connect the agency for the other, the direct connection breaks with the first agency. Any guidance or feedback on this? I appreciate you guys.
1 like • 12d
@Wateeb Khan thank you!
Workshop Wednesday
@Jorden Williams @Mike Copeland is this still on?
0 likes • 12d
In waiting room
Life Insurance niche
would love to connect with people in the life insurance niche to see how you’re implementing AI and what success you’re seeing
1 like • 13d
im in the life insurnace niche!
1-10 of 13
Dylan Essad
2
8points to level up
@dylan-essad-2814
solving problems

Active 1d ago
Joined Jan 15, 2026
Florida
Powered by