# Connect your AI agents to HighLevel and your business tools. Connect HighLevel, calendars and your own APIs. Give agents the context to answer, the tools to act and a clear path into the systems your team already uses. ## What it does ### Voice and chat AI for HighLevel Connect authorized HighLevel subaccounts for inbound calls, outbound follow-up and appointment booking. Agents use contact context, update details and book into connected calendars with the appropriate tools. - Built-in HighLevel connection - Contacts, conversations and calendars - Authorization and setup per subaccount ### Put your other systems to work Let an agent look up an order, update a CRM record or open a support ticket through a configured HTTP tool. Define the endpoint, credentials and inputs, then return the result to the conversation. - Custom CRM, ERP and service workflows - API configuration and data mapping required - Tools for voice and chat agents ### Turn interest into a booked time Connect scheduling to the conversation. Scope availability, booking and changes around your calendar provider, account type and required appointment details. - Google Calendar and Microsoft Outlook - Calendly, Cal.com and HighLevel - Provider permissions and plan requirements apply ### Run without HighLevel Assistable Direct keeps contacts, conversations and messages in Assistable. Use the v3 API and custom tools to connect your own application without requiring a HighLevel account. - Native contact and conversation records - Scoped API access by subaccount - Confirm the booking route for your account type ## Deployment lifecycle ### Connect Choose the target subaccount, authorize its connections and map the fields each action needs. Give tools only the credentials and permissions required for that task. ### Validate Use test records to verify a lookup, an update and a booking in the destination system. Check missing fields, expired access and an unavailable endpoint before releasing the flow. ### Publish Release the tested agent flow. Confirm the live tool assignments and destination accounts, then start with a controlled set of conversations. ### Observe Review the conversation alongside its tool result and destination record. Confirm that a successful conversation also produced the intended business action. ## Under the hood - **Built-in HighLevel:** Connect authorized HighLevel subaccounts for contacts, conversations and calendars. Select the correct location and calendar, attach the required tools and verify the result on a test contact. - **Configured API workflows:** Connect other CRMs, ERPs and internal services through HTTP tools and webhooks. Each custom workflow is scoped to the endpoints, credentials, permissions and data mappings your system provides. - **Assistable API:** The public v3 API supports assistants, contacts, conversations, tools, calls and other resources. Keys carry resource and action scopes, and requests select an authorized subaccount with X-Subaccount-Id. - **Calendar requirements:** Scheduling connections include HighLevel, Google Calendar, Outlook, Calendly and Cal.com. Available actions depend on your account type, provider permissions and plan. The public v3 Appointments resource is currently HighLevel-scoped; confirm a separate booking workflow for Assistable Direct. ## Implementation guides - [Assistable on the HighLevel marketplace](https://marketplace.gohighlevel.com/integration/654f0a0b27d2b916226b8337/versions/654f0a0b27d2b916226b8337): View the official app listing, calling and messaging providers, and workflow actions. - [Connect a HighLevel subaccount](https://docs.assistable.ai/integrations/ghl-oauth): Authorize the connection and verify the account in your workspace. - [Plan your HighLevel AI workflows](/integrations/gohighlevel): Review calling, booking, account setup and verification in one integration guide. - [Build a custom tool](https://docs.assistable.ai/build/custom-tools/overview): Define the task, endpoint, authentication and input parameters. - [Configure a support-ticket workflow](https://docs.assistable.ai/build/custom-tools/submit-ticket): Collect the details, submit the ticket and validate the result. - [Use Assistable without HighLevel](https://docs.assistable.ai/direct/overview): Understand Direct accounts, native records and current API limits. - [Start with the v3 API](https://docs.assistable.ai/v3/introduction): Find the base URL, request conventions and interactive reference. - [Scope access to the right accounts](https://docs.assistable.ai/v3/authentication): Set resource permissions and select an authorized subaccount. ## Related workflows - [White-label AI for HighLevel agencies](https://www.assistable.ai/agency): Brand the client portal, manage accounts and configure rebilling. - [Outbound follow-up from HighLevel](https://www.assistable.ai/platform/campaigns): Use workflow triggers and campaign controls to reach eligible contacts. - [Replacing SimpleTalk](https://www.assistable.ai/compare/simpletalk): Compare calling, booking and client-account workflows. - [Reuse reviewed AI agent deployments](https://www.assistable.ai/blog/reusable-ai-agent-deployments): Map reusable assistant configurations to each destination account’s calendars and eligible tools. - [Custom cards for tool results](https://www.assistable.ai/blog/ai-card-builder): Use Card Builder to present connected data in branded cards for customer conversations. ## FAQ **Does Assistable require GoHighLevel?** No. Assistable offers a built-in HighLevel connection and Assistable Direct, which stores contacts, conversations and messages in Assistable. Direct supports the v3 API and custom tools without a HighLevel account. Booking needs a separate check: the public v3 Appointments resource is currently HighLevel-scoped. **Can we keep our current CRM and business systems?** Yes. HighLevel has a built-in connection. Other systems can connect through configured API tools and webhooks where the required endpoints and permissions are available. We will scope the actions and data mapping with your team. **Does every integration come ready to use?** Built-in connections still require your account authorization and setup. Custom API workflows require endpoint configuration, credentials, data mapping and validation. We will confirm which approach fits each system before deployment. **How would an agent open a ticket in our support system?** Configure a custom tool with your ticket endpoint, credentials and required fields. Instruct the agent when to use it and what details to confirm first. Test with a sample conversation, inspect the tool response and verify the ticket in your system. A configured endpoint and the required API permissions are necessary. **Can our development team manage agents through an API?** Yes. Use the public API at api.assistable.ai/v3 with a scoped API key. Select the target subaccount using X-Subaccount-Id and grant the resource and action scopes your integration needs. The documentation includes an interactive reference, TypeScript and Python SDKs, a CLI and an MCP server. **Can we test changes before customers encounter them?** Yes. Test tool requests and draft agent flows before publishing, using test accounts or endpoints for actions that change data. Published flow versions and working branches let your team prepare changes separately from the live flow. **What happens if a connection fails?** Define what the agent should do when a tool cannot complete its task, such as request missing information, offer a follow-up or escalate to a person. Test that path alongside the successful one. Retry behavior differs by integration, so verify the destination record before repeating an action that could create a duplicate. --- Source: https://www.assistable.ai/platform/integrations