Jrocks
Jrocks5mo ago

Jrocks - Hi BuildShip,I use GoHighLevel CRM, ...

Hi BuildShip, I use GoHighLevel CRM, which uses OAuth 2. I need some direction on how to integrate it with BuildShip. I'm planning to use BuildShip to utilize OpenAI functionality, primarily as an AI receptionist that books appointments conversationally. This requires access to GHL's API 2.0 to get calendar slots and create appointments. I work with local businesses and agencies, so ideally, I would like to use BuildShip as my hub where I can create AIs for my clients. Please advise or point me in the right direction on how to get started with this on your platform. Here's the GHL API 2.0 documentation: https://highlevel.stoplight.io/docs/integrations/0443d7d1a4bd0-overview
Overview | Integrations API
These APIs use OAuth 2.0 flow for authentication. Powered by Stoplight.
Solution:
HI @Jrocks, You can use the AI node generator to create a node for GHL or use the API Callnode to make a call to their endpoint as I've seen they have REST APis avaible to make direct call to instead of OAuth for now. - https://docs.buildship.com/ai-nodes
AI Generated Nodes – BuildShip
A unified resource to start building your backend with low-code. Dive into triggers, nodes, and step-by-step guidance to jumpstart your workflow creation.
Jump to solution
2 Replies
Solution
Gaurav Chadha
Gaurav Chadha4mo ago
HI @Jrocks, You can use the AI node generator to create a node for GHL or use the API Callnode to make a call to their endpoint as I've seen they have REST APis avaible to make direct call to instead of OAuth for now. - https://docs.buildship.com/ai-nodes
AI Generated Nodes – BuildShip
A unified resource to start building your backend with low-code. Dive into triggers, nodes, and step-by-step guidance to jumpstart your workflow creation.
Jrocks
Jrocks4mo ago
I was hoping to avoid using their REST API because they charge per request. You can imagine how quickly the costs could add up with frequent use of the AI assistant, especially given the high volume of back-and-forth requests typical in conversation messaging. That's why I'm interested in going the OAuth 2 route, as there's no cost associated per request. Thanks for the response, though. I'll keep an eye out for when BuildShip creates a direct integration with GHL.