Doing some work on tool initializaiton and reference mapping to help with direct API calls and even filtering data you want sent back to the assistant - should see the mapping and request builder go into production tomorrow

**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

If I bring my own key, it still costs the same compared to if I used Assistable's key, yeah?

Hey lovely community! A few of you were asking about how to reliably extract any required information from users while the AI is actively having a conversation beyond just basic name, email, and phone. While we already have tools for standard fields, the most powerful and reliable approach for advanced, custom, or business-specific data collection is using Automatic Data Extraction (Map Custom Fields) instead of Extraction Tools. Here's the guide on how to do it- https://help.assistable.ai/how-to/how-to-gather-and-extract-important-user-information-using-automatic-data-extraction @Ryan B hope you find this useful. This directly solves the data capture reliability issue you were facing

Hey Assistable community — here’s a quick, unofficial Assistable Voice (Outbound Call) API cheat sheet. Disclaimer: I don’t work for Assistable and this isn’t official or supported by me. Sharing only because people want a copy-paste example and the docs are thin/outdated in places. Use at your own risk. ✅ The Voice endpoint (outbound call) POST https://api.assistable.ai/v2/ghl/make-call Headers Authorization: Bearer asst_YOUR_V2_KEY ← v2 keys start with asst_ Content-Type: application/json Copy-paste curl curl -sS -X POST "https://api.assistable.ai/v2/ghl/make-call" \ -H "Authorization: Bearer asst_YOUR_V2_KEY" \ -H "Content-Type: application/json" \ -d '{ "assistant_id": "YOUR_ASSISTANT_ID", "location_id": "YOUR_LOCATION_ID", "contact_id": "YOUR_CONTACT_ID" }' Expected behavior If it works, you’ll get: "success": true a "call_id" you can store If it fails, you’ll still get a response, usually one of these: No outbound number on assistant Contact has no phone Phone is on public DNC list That’s the whole flow for MVP voice.