HubSpot을 Excel에 연결하는 방법 - SQL로 CRM 데이터 쿼리하기

HubSpot과 Excel을 연결하세요

다음에서 데이터를 가져오세요 HubSpot ~ 안으로 Excel

HubSpot 계정에서 실시간으로 데이터를 가져와 Excel로 불러오고 원할 때마다 새로 고칠 수 있습니다. ODBC 드라이버, 내보내기, 매크로가 필요 없습니다. 처음 설정하는 데 약 10분 정도 소요되며, 무료 플랜에서 모두 이용 가능합니다.

약 10분 코딩이 필요 없습니다 자격증명은 영구적으로 보관됩니다. 웹에서도 엑셀을 사용할 수 있습니다.

당신이 최종적으로 얻게 될 것

HubSpot 계정에 대한 SQL 쿼리 결과를 실시간으로 보여주는 워크시트입니다. 데이터가 변경될 때마다 최신 행을 가져오는 버튼도 있습니다. 예를 들어 다음과 같습니다.

판매.xlsx — 엑셀

홈끼워 넣다데이터쿼리 스트림

	A	B	C	D	E
1	customer_id	첫 번째 이름	성	국가	총
2	1042	마리아	알바레스	미국	1,284.50
3	1043	다니엘	오카포르	미국	612.00
4	1047	프리야	나이르	미국	2,090.75
5	1051	도마	산	미국	338.20
6	1056	루시아	페레이라	미국	1,455.00
7	1060	켄지	사토	미국	874.10
8

시트1 HubSpot에서 생중계

HubSpot은 API를 통해 데이터를 관리합니다. 일반적으로 최신 데이터가 필요할 때마다 HubSpot 대시보드에서 CSV 파일로 내보내야 Excel로 가져올 수 있습니다. 하지만 Query Streams를 사용하면 이 과정을 생략할 수 있습니다. Agent라는 작은 도우미 프로그램이 데이터가 저장된 위치에서 쿼리를 실행하고, Excel 추가 기능이 필요한 행을 요청합니다. 암호화된 링크를 통해 결과만 전송되므로 Excel 파일은 어디에 있든 상관없습니다. 집의 노트북, 멀리 떨어진 동료의 컴퓨터, 또는 웹 기반 Excel 등 어디에서든 사용할 수 있습니다.

필요한 것

Query Streams 계정

이 가이드를 이용하시려면 무료 플랜으로도 충분합니다. 지금 가입하세요. my.querystreams.com.

항상 켜져 있는 컴퓨터의 에이전트

백그라운드에서 실행되는 작은 프로그램으로, Excel에서 HubSpot 호출을 요청할 때 작동합니다. 인터넷 연결만 있으면 됩니다.

HubSpot 로그인 정보

HubSpot에 한 번 로그인하고 읽기 권한을 허용하면 됩니다. 쿼리 스트림에는 비밀번호를 입력할 필요가 없습니다.

5단계로 연결하세요

1. 계정을 만드세요

   가다 my.querystreams.com 가입하세요. 선택하세요. 무료 정식 플랜입니다. 체험판이 아니며, HubSpot 계정 연결 및 Excel에서 쿼리 실행 기능을 포함합니다.

2. 항상 켜져 있는 컴퓨터에 에이전트를 설치하십시오.

   로그인, 열기 다운로드인터넷에 접속할 수 있는 상시 가동 컴퓨터 또는 서버에 에이전트를 설치하십시오. 설치에는 약 1분 정도 소요되며, 이후에는 자동으로 시작됩니다.

   드라이버 대신 작은 프로그램을 사용하는 이유는 무엇인가요? 에이전트는 Windows, Mac 또는 Linux용으로 한 번만 설치하면 되며(Windows에서는 약 85MB, Mac 및 Linux에서는 100MB 조금 넘는 용량), 백그라운드에서 조용히 실행됩니다. 웹 브라우저와 마찬가지로 쿼리 스트림에 암호화된 연결을 한 번만 생성하므로 방화벽 포트를 열거나 VPN을 설정할 필요가 없습니다. 키는 해당 컴퓨터에 보관되며, 데이터는 필요한 경우 인터넷을 통해 사용자의 위치로 전송됩니다. 사용자가 해야 할 일은 추가 기능 설치뿐입니다.

   다운로드 페이지가 표시됩니다 액세스 키에이전트가 요청할 때 해당 코드를 붙여넣고 배지가 인식될 때까지 기다리세요. 쿼리 스트림에 연결됨에이전트 자체에서 할 수 있는 일은 그게 전부입니다.

   자세한 공략이 필요하시면 보여드리겠습니다. 윈도우, 스코틀랜드 사람, 리눅스.

3. HubSpot 계정을 지정하세요

   브라우저로 돌아가서 열기 데이터 에이전트 (아래에 데이터 상단 메뉴에서 담당 에이전트를 확인하세요. (상단 메뉴에 있습니다.) 커넥터 추가 그리고 선택하세요 HubSpot. Need your HubSpot credentials first? Open the walkthrough, then fill in:

   Create your HubSpot credentials (about 5 minutes)

   Follow this with HubSpot open in another tab. Query Streams keeps what you create here so your Agent can use it, and only ever reads from HubSpot.

   Who can do this

   Super admin, or a user with the Developer tools access permission (service keys). Legacy private apps need a Super admin.

   추천

   Service key with read-only scopes (Development → Keys → Service Keys). HubSpot recommends service keys for scheduled data syncs to BI tools and warehouses, and is removing the option to create new legacy private apps.

   시작하기 전에

   • A HubSpot login that is a Super admin or has the Developer tools access permission. A service key can only be given scopes your own HubSpot user already has.
   • Know which HubSpot account you want to query. A key only reads the account it was created in, so create it in that account, not in a test or sandbox account.
   • Decide which HubSpot tables you want. Contacts, Companies, Deals, Owners, Pipelines, Pipeline Stages and Properties are on by default; every extra table needs its own read scope (see Permissions).
   • The Query Streams Agent installed and online on an always-on computer, and the Query Streams portal open in another tab: Data Agents → Add connector → HubSpot.

   Steps

   1. Sign in to HubSpot

      Open HubSpot in a new tab and sign in as a Super admin, or as a user with the Developer tools access permission.

      If you belong to more than one HubSpot account, switch to the one whose data you want before you continue. The key only works for the account it is created in.

   2. Open Development

      In the left main navigation, near the bottom, click Development (the </> icon). The Development page opens with its own sidebar: Overview, Projects, Legacy Apps, Monitoring, Keys and more.

      No Development item? Your HubSpot user is not a Super admin and lacks Developer tools access. Ask a Super admin to create the key, or to give you that permission.

   3. Open Service Keys

      In the Development sidebar, click Keys to expand it, then click Service Keys (it has a Beta badge). The Service Keys page opens; if you have none yet it says No Service Keys Created.

      Do not use Personal Access Key or Developer API Key, which sit just above Service Keys in the same menu. They are developer-tool keys and will not connect. Some accounts also reach this page from Settings (gear icon) → Integrations → Service Keys.

   4. Click Create service key

      In the top right of the Service Keys page, click Create service key. The Create Service Key page opens with a Name box and a Scopes section.

   5. Name the key

      In Name, type a name you will recognise later, for example Query Streams read-only. HubSpot shows this name in its logs.

      The name must be unique in your HubSpot account.

   6. Open the scope picker

      Next to Selected scopes, click + Add new scope. A panel opens on the right with a Find a scope search box and a checkbox for each scope.

   7. Tick the four required scopes

      Type each name into Find a scope and tick its checkbox: crm.objects.contacts.read, crm.objects.companies.read, crm.objects.deals.read, crm.objects.owners.read. These four cover every table Query Streams syncs by default.

      Tick only scopes that end in .read. Query Streams only reads from HubSpot; it never needs a .write scope.

   8. Tick scopes for any extra tables

      For each extra table you want, tick its scope from the Permissions list below. For example: crm.objects.tickets.read for Tickets; crm.objects.line_items.read for Line Items, Taxes, Discounts and Fees; crm.lists.read for Lists. Skip this step if the default tables are enough.

      You can add scopes later without making a new key (open the key, then Edit).

   9. Click Update

      Click Update in the right panel. The panel closes and your scopes are listed under Selected scopes.

   10. Check the scope list

       Read through Selected scopes. If anything ends in .write, click Delete next to it. Expand Summary of selected scopes if you want a plain-language list of what the key can see.

   11. Create the key

       Click Create in the top right, then confirm in the dialog box that opens.

   12. Open your new key

       Go to Development → Keys → Service Keys and click the name of the key you just created. Its details page opens with a Service Key box.

   13. Show and copy the key

       In the Service Key box the value is partly hidden and starts with pat- (for example pat-na1-…). Click Show under it, then click Copy.

       Use Copy rather than selecting the text by hand: a missing character, a trailing space or the hidden dots will fail the test. HubSpot does not show the key only once; you can come back and click Show again. Treat it like a password.

   14. Paste it into Query Streams and test

       In the Query Streams portal open Data Agents, click Add connector and choose HubSpot. Paste the key into App Access Token, type a Connection name, then click Test connection. The result reads Connected.

       Query Streams stores the key for your Agent and only ever reads your HubSpot data.

   15. Match the tables to your scopes

       On the Sync step that follows, leave on only the HubSpot tables whose scopes you ticked in steps 7 and 8, then finish the wizard.

       A table switched on without its scope fails to sync with a Forbidden error. Add the scope to the key (step 8) or switch the table off.

   Alternatives

   Use a legacy private app token

   Your account already has a legacy private app you want to reuse. HubSpot is removing the option to create new ones: accounts created on or after 28 September 2026 already cannot, and older accounts lose it on 26 October 2026. Existing private apps and their tokens keep working.

   Who can do this: Super admin

   1. Open Legacy Apps

      In HubSpot click Development in the left main navigation, then Legacy Apps in the Development sidebar.

      Older HubSpot navigation called this Settings → Integrations → Private Apps.

   2. Open your private app, or start a new one

      If the app is listed, click its name and go to step 6 (or step 5 to add scopes). If not, and the button is still there, click Create legacy app in the top right and choose Private in the dialog box.

      No Create legacy app button means creation is already switched off for your account. Use a service key (main steps) instead.

   3. Name the new app

      On the Basic Info tab, enter a name such as Query Streams read-only. The logo and description are optional.

   4. Add the read scopes

      Click the Scopes tab, click Add new scope, tick the same scopes as in main steps 7 and 8, then click Update. Then click Create app in the top right, read the access-token message in the dialog box and click Continue creating.

   5. Add scopes to an existing app (only if needed)

      On the app’s page click Edit app in the top right, open the Scopes tab, add the missing read scopes and save. The token string does not change when you change scopes.

   6. Show and copy the token

      On the app’s page click the Auth tab. Under Access token click Show token, then click Copy. The token starts with pat-. Paste it into App Access Token as in main step 14.

      If the HubSpot user who created the app is removed from HubSpot, some calls fail with USER_DOES_NOT_HAVE_PERMISSIONS. Rotate the token (Rotate next to it) and paste the new one, or move to a service key.

   Use a developer-platform app’s static auth token

   Your team has already built a HubSpot app on the new developer platform with the HubSpot CLI, configured with static auth and private distribution. Building one needs the CLI; if you don’t have one, use a service key.

   Who can do this: Super admin, or a user with a developer seat, to view the token; Super admin or the HubSpot Marketplace access permission to install the app

   1. Open the project

      In HubSpot click Development, then Projects in the sidebar, then the name of the project that holds your app.

   2. Open the app

      On the project’s Overview tab, under Project Components, click the app’s name.

   3. Open the Distribution tab

      Click the Distribution tab.

   4. Install the app if it isn’t yet

      Under Manage distribution your current HubSpot account is listed. Click Install now, check that the access requested matches the read scopes you configured, then click Connect app.

      A static-token app can be installed in only one standard HubSpot account at a time.

   5. Show and copy the token

      Once installed, the Distribution tab shows an access token. Click Show to reveal it, copy it, and paste it into App Access Token as in main step 14.

      If you change the app’s scopes later, reinstall it with the Reinstall URL on the Distribution tab, or the new scopes won’t apply.

   Permissions to grant

   Resource	액세스	Used for
   crm.objects.contacts.read	읽다	Required. hubspot.contacts, plus the activity tables hubspot.calls, hubspot.emails, hubspot.meetings, hubspot.notes, hubspot.tasks and hubspot.communications (HubSpot’s activity APIs use this scope), and contact fields in hubspot.properties and hubspot.associations.
   crm.objects.companies.read	읽다	Required. hubspot.companies, and company fields in hubspot.properties and hubspot.associations.
   crm.objects.deals.read	읽다	Required. hubspot.deals, the deal pipelines in hubspot.pipelines and hubspot.pipeline_stages, and deal fields in hubspot.properties and hubspot.associations.
   crm.objects.owners.read	읽다	Required. hubspot.owners, the HubSpot users who own records, so deals and contacts can be joined to a rep’s name.
   crm.objects.tickets.read	읽다	Only if you sync Tickets: hubspot.tickets and the ticket pipelines in hubspot.pipelines and hubspot.pipeline_stages. Older apps may show the legacy tickets scope instead, which also allows changes.
   crm.objects.products.read	읽다	Only if you sync Products: hubspot.products. Search the picker for products; HubSpot’s products API accepts this scope, although HubSpot’s scope reference page does not list it yet.
   crm.objects.line_items.read	읽다	Only if you sync Line Items, Taxes, Discounts or Fees: hubspot.line_items, hubspot.taxes, hubspot.discounts, hubspot.fees.
   crm.objects.quotes.read	읽다	Only if you sync Quotes: hubspot.quotes.
   crm.objects.invoices.read	읽다	Only if you sync Invoices: hubspot.invoices.
   crm.objects.subscriptions.read	읽다	Only if you sync Subscriptions: hubspot.subscriptions (HubSpot commerce subscriptions).
   crm.objects.commercepayments.read	읽다	Only if you sync Payments: hubspot.payments (HubSpot commerce payments).
   crm.objects.marketing_events.read	읽다	Only if you sync Marketing Events: hubspot.marketing_events.
   forms	Read and write (HubSpot has no read-only forms scope)	Only if you sync Forms or Form Submissions: hubspot.forms and hubspot.form_submissions. Query Streams only reads them.
   crm.objects.feedback_submissions.read	읽다	Only if you sync Feedback: hubspot.feedback_submissions. Service Hub Professional or Enterprise only. HubSpot’s scope reference spells it crm.objects.feedback_submission.read, so search the picker for feedback.
   crm.lists.read	읽다	Only if you sync Lists: hubspot.lists.
   오토메이션	Read and write (HubSpot has no read-only workflows scope)	Only if you sync Workflows: hubspot.workflows. Professional or Enterprise accounts only. Query Streams only reads workflow definitions.
   crm.schemas.custom.read	읽다	Only if you sync Custom Schemas: hubspot.schemas (custom object definitions). Enterprise accounts only.

   Paste into Query Streams

   앱 액세스 토큰

   The service key you copied in step 13 (it starts with pat-), or a legacy private app token, or a developer-platform app’s static auth token

   Common problems

   Test connection fails with Invalid or expired access token, straight after you pasted a new key.

   Why: The value is not an app or service key. The usual mix-up is the Personal Access Key or Developer API Key, which sit next to Service Keys under Development → Keys and are for HubSpot’s developer tools.

   Fix: Go to Development → Keys → Service Keys, open your key, click Show, then Copy, and paste that into App Access Token. Test connection again; it reads Connected.

   The wizard says Not a valid HubSpot app token before it even tests.

   Why: Only part of the key was pasted: the text doesn’t start with pat- and is very short or contains a space.

   Fix: Back in HubSpot click Show, then use the Copy link (don’t select the text by hand) and paste again.

   You can’t see Development in HubSpot’s left navigation, or Service Keys is missing under Keys.

   Why: Your HubSpot user is not a Super admin and doesn’t have the Developer tools access permission.

   Fix: Ask a Super admin in your company to create the key (steps 2 to 13) and paste it into the wizard, or to grant you Developer tools access.

   Test connection reads Connected, but one table fails to sync with a Forbidden error or stays empty.

   Why: The key is missing the read scope for that table, or your HubSpot plan doesn’t include that feature (Workflows needs Professional or Enterprise; Custom Schemas needs Enterprise; Feedback needs Service Hub Professional or Enterprise).

   Fix: Open the key (Development → Keys → Service Keys → key name), click Edit, add the scope from the Permissions list and save, then sync again. If your plan doesn’t include the feature, switch that table off in the connection’s Sync settings.

   Syncs that used to work start failing with Invalid or expired access token.

   Why: Someone rotated or deleted the key. Rotate and expire now stops the old key at once; Rotate and expire later stops it after 7 days.

   Fix: Copy the current key from Development → Keys → Service Keys → key name → Show → Copy. In Data Agents, edit the HubSpot connection, paste it into App Access Token and run Test connection.

   With a legacy private app token, some tables fail with USER_DOES_NOT_HAVE_PERMISSIONS.

   Why: The HubSpot user who created the private app was removed from the account.

   Fix: Rotate the app’s token (Development → Legacy Apps → app → Rotate) and paste the new token into the connection, or create a service key instead.

   You can’t find Create legacy app, or HubSpot’s docs call private apps legacy.

   Why: HubSpot is retiring creation of new legacy private apps (already off for accounts created on or after 28 September 2026; off for older accounts from 26 October 2026). Existing private apps keep working.

   Fix: Create a service key (main steps). Existing private app tokens can stay in place.

   Data in Query Streams doesn’t match what you see in HubSpot.

   Why: The key was created in a different HubSpot account (for example a test or sandbox account).

   Fix: Switch to the right HubSpot account, create a key there, and paste it into the connection.

   Limits to know

   • HubSpot’s limits for service keys and private apps: 100 requests per 10 seconds per key on Free and Starter, 190 on Professional and Enterprise, 250 with the API Limit Increase add-on. The Agent paces itself to the lowest of these, so the first full sync of a large CRM can take a while.
   • Daily limit per HubSpot account: 250,000 requests on Free and Starter, 625,000 on Professional, 1,000,000 on Enterprise. It is shared by every private app and service key in the account, so other integrations use the same budget.
   • HubSpot’s CRM search, which the Agent uses to fetch only changed records, allows 5 requests per second per account and at most 10,000 results per query.
   • Some tables depend on your HubSpot plan: Workflows (Professional or Enterprise), Custom Schemas (Enterprise), Feedback (Service Hub Professional or Enterprise).
   • Service keys are in public beta (since 10 February 2026), so HubSpot may change details. HubSpot recommends rotating keys every six months.
   • New legacy private apps can’t be created in accounts made on or after 28 September 2026, nor in older accounts from 26 October 2026. Existing apps and tokens keep working.

   Steps verified 8 October 2026. Sources: developers.hubspot.com/docs/apps/developer-platform/build…, developers.hubspot.com/changelog/service-keys, developers.hubspot.com/blog/hubspot-service-keys-the-righ…, developers.hubspot.com/changelog/legacy-private-app-creat…, developers.hubspot.com/docs/apps/legacy-apps/private-apps…, developers.hubspot.com/docs/apps/developer-platform/build…, developers.hubspot.com/docs/apps/developer-platform/build…, developers.hubspot.com/docs/apps/developer-platform/build…, developers.hubspot.com/docs/getting-started/developer-ove…, developers.hubspot.com/docs/apps/developer-platform/build…, developers.hubspot.com/docs/developer-tooling/platform/us…, developers.hubspot.com/docs/api-reference/latest/crm/sear…, knowledge.hubspot.com/user-management/hubspot-user-permis…, developers.hubspot.com/docs/api-reference/legacy/crm/obje…, developers.hubspot.com/docs/api-reference/legacy/crm/acti…, developers.hubspot.com/docs/api-reference/legacy/crm/acti…, developers.hubspot.com/docs/api-reference/legacy/crm/obje…, developers.hubspot.com/docs/api-reference/legacy/crm/obje…, developers.hubspot.com/docs/api-reference/legacy/crm/pipe…, developers.hubspot.com/docs/api-reference/legacy/crm/obje…, developers.hubspot.com/docs/api-reference/legacy/automati…, developers.hubspot.com/docs/api-reference/legacy/marketin…, developers.hubspot.com/docs/api-reference/legacy/account/…, docs.n8n.io/integrations/builtin/credentials/hubspot.

   연결 이름

   나중에 알아볼 수 있는 이름들입니다. 예를 들어, 판매 데이터베이스 같은 것이죠.

   앱 액세스 토큰

   HubSpot 비공개 앱 토큰(pat-으로 시작)은 설정 > 통합 > 비공개 앱 > 앱 > 인증 탭에서 찾을 수 있습니다.

   클릭 테스트 연결읽을 때 연결됨클릭 저장연결은 몇 초 내에 에이전트에 도달합니다.

   오픈 데이터 에이전트

   테스트에 실패했나요? Usually a missing permission, or a credential from the wrong HubSpot account. The walkthrough above lists the common problems and their fixes.

4. Excel에 쿼리 스트림 추가

   엑셀에서 다음으로 이동하세요. 삽입 → 추가 기능 가져오기검색하세요 쿼리 스트림그리고 클릭하세요 추가하다또는 바로 열어보세요. Microsoft AppSource에서 Query Streams를 검색하세요.리본 메뉴에 '스트림 쿼리' 버튼이 나타납니다. 동일한 계정으로 로그인하세요.

   Windows 및 Mac용 Microsoft 365 Excel과 웹 버전 Excel에서 작동합니다.

5. 첫 번째 테이블을 가져오세요

   "쿼리 스트림" 버튼을 클릭하고 선택하세요. 쿼리를 스트리밍하세요그리고 방금 연결한 연결을 선택하세요.

   실행하려는 쿼리를 입력하세요. 이 쿼리는 테이블에서 몇 개의 열을 가져옵니다. 허브스팟딜 테이블:

   예시 · SQL

   hubspot.deals 테이블에서 dealname, dealstage, amount, closedate를 closeate 기준으로 내림차순으로 정렬하고, 개수 제한을 100으로 설정합니다.

   아래에 목적지 정보 선택하다 새 시트를 만드세요그런 다음 재생 버튼(▶ 화살표)을 누르세요. 1~2초 안에 행이 Excel에 나타납니다. 데이터가 변경될 때마다 재생 버튼을 다시 누르면 시트가 자동으로 업데이트됩니다.

   SQL을 모르시나요? 쿼리 스트림 포털에서 쿼리를 작성하세요. 쿼리 빌더 테이블과 열을 표시해 주므로 마우스 클릭만으로 원하는 정보를 찾을 수 있습니다. 비즈니스 플랜에서는 Nova에 "미국 고객을 보여주세요"와 같이 간단한 영어로 요청하면 Nova가 SQL 쿼리를 자동으로 작성해 줍니다. 쿼리를 저장하면 포털에서 한 번의 클릭으로 바로 사용할 수 있으며, Personal Core 플랜 이상부터는 추가 기능의 저장된 쿼리 목록에서도 확인할 수 있습니다.

좋은 다음 행보입니다

• 쿼리를 저장하세요 포털에 저장되므로 엑셀이나 구글 시트에서 한 번의 클릭으로 다시 실행할 수 있습니다.
• 필터를 추가하세요 날짜 범위를 지정할 수 있으므로 편집 없이 동일한 쿼리로 "이번 달"이라는 답변을 얻을 수 있습니다.
• 결과를 공유하세요 동료와 함께 있을 때, 그들은 당신의 자격 증명이 아니라 행 목록만 봅니다.

사람들이 묻는 질문

관련 가이드

• HubSpot에서 Google Sheets로
• Stripe에서 Microsoft Excel로
• Shopify에서 Microsoft Excel로
• Google Analytics 4에서 Microsoft Excel로
• Excel에서 SQL 실행하기
• 모든 가이드