> For the complete documentation index, see [llms.txt](https://docs.drivepoint.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.drivepoint.io/data-integrations/pro-tips-and-tricks.md). # Pro Tips & Tricks Data integrations inform your everything you can find in the Drivepoint Platform and the SmartModel™️. Find out tips & tricks👇 {% embed url="" %} Learn the basics of connecting Shopify, Quickbooks, etc {% endembed %} **Pro Tip 1:** Quickbooks (QBO) is very easy to connect to Drivepoint. Connect it in a few minutes to help stand up your model! *Skip this step if your company is not on QBO.* If you are logged in the [Drivepoint web app](https://app.drivepoint.io/), click on data sources and then on Quickbooks. It should open up a dialogue in the window. After logging into Quickbooks and accepting the permissions you are all set. **Pro Tip 2:** You do not need to be the owner of the Shopify account to connect it to Drivepoint We have recently updated the permissions necessary to connect your Shopify account to Drivepoint and benefit from importing Direct-to-Consumer data to inform your forecasts. If you are not the owner, find out what specific permissions you need [here](/data-integrations/shopify.md). --- # 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://docs.drivepoint.io/data-integrations/pro-tips-and-tricks.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.