> For the complete documentation index, see [llms.txt](https://help.doctorlogic.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.doctorlogic.com/docs/extensions/hubspot.md). # HubSpot This integration lets you automatically sync new leads from your DoctorLogic website into your HubSpot account. We know that many of our customers use a variety of patient management and customer relationship management tools to run their practice. As a result, we are always looking for ways to integrate DoctorLogic into those applications to add additional value to your existing business workflows.\ \ This is exactly why we built our **new integration with HubSpot,** one of the leading providers in the CRM space. Now when new leads fill out a form on your website they will be automatically synced into your HubSpot account.\ \ No more exporting and importing. No more tedious, manual data entry. After a one-time set up you can sit back and let the automation handle the rest!\ \ ​​​​- Our team will walk you through the step-by-step process to get the integration configured\ \ \- Once leads fill out the form on your site, the data will populate inside your DoctorLogic account and then be instantly added into your HubSpot account\ \ \- Create custom reports inside HubSpot to organize your new leads and then follow up For additional information please contact --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://help.doctorlogic.com/docs/extensions/hubspot.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.