Came across this in my research... It's a template to create your own market place server like GHL's - GoHighLevel/ghl-marketplace-app-template: The official template provided by GoHighLevel for deploying your own Marketplace App server on platforms like Render.Link: https://github.com/GoHighLevel/ghl-marketplace-app-template

@Mike Copeland Hey, Is the ability for the client to manage their assistable subscription and usage in their GHL account in the roadmap? [I already added this to the feature request]. Thanks

**This post is for the technical builders** For those who dont use tooling -- its the actual key for enterprise use cases and its the biggest differentiator, even internally, as you chase big projects / clients. We have set up abilities using tools, middleware and external database that you wouldn't even believe and they are very high ticket (think north of $50k), I suggest its something to take a look at if you haven't before So, as we build alongside you for fulfillment we noticed some limitations that I think needed to be addressed. So, here is the basis of those additional functionalities: post / put / patch / get / delete, execution type (proxy, direct, workflow execution), headers, timeout MS, flattened tool menu to a page not a popup Proxied tool calls is your traditional tool call for middleware as you see it today. Output is wrapped in an args object with a meta_data object. These are best suited for middleware usage (make, n8n, buildship, etc) because not only do you have your agent's output but you have location id, contact id, etc. Direct tool calls are exactly that - we dont wrap it in anything - we just send the raw request exactly as you have configured it. This is for when you want to attach to something like an MLS, or niche API directly. Cofigure headers (variable friendly), configure body parameters (and soon query parameters), and the http type. We'll send the request on your behalf just as you would anywhere and return the direct output. Workflow execution is for the internal workflow engine we are adding so we can supply you with a middleware if you dont already have one, or looking for something more native to our functinoality. more to come, happy thursday

Can Assistable reply to emails now with the customer replied trigger and active tag? Anyone having success here?

I’m running into an issue where the assistant pulls scheduling info from a contact, but after a database reactivation it starts mixing things up and returning incorrect times. Is there a way to automatically clear a specific contact’s conversation history? Keeping all the old context is actually hurting the workflow, and I’m already seeing it negatively affect my accounts. Ideally, I’d like to trigger this with something like a webhook in a workflow or a workflow action that clears the conversation history for that contact. Thanks @Jorden Williams, @Mike Copeland