---
title: HubSpot Integration FAQ
slug: hubspot-integration-faq
createdAt: 2026-07-13T14:33:14.104Z
---

## Getting Started

**What does the HubSpot integration do?**
It connects your HubSpot deals to AWSsome, so your sales pipeline and your AWS co-sell work stay in sync. AWSsome pulls deals from up to 3 HubSpot pipelines into a queue. Your own team reviews each deal there and submits it to AWS Partner Central. After that, stages sync both ways, and AWS's status, score and advice show on the HubSpot deal. When you accept an opportunity that AWS shares with you, AWSsome creates the deal in HubSpot.

**What do I need before I connect?**

- An AWSsome account with deal registration turned on.
- Super Admin or App Marketplace access permissions in HubSpot. Without them, you can ask an admin with Request to install on the app listing.
- A HubSpot plan that has the pipelines you want to sync. HubSpot's free tools have only the default deal pipeline, so syncing more than one pipeline needs Starter or above.

**Can I install the app from the HubSpot Marketplace?**
Yes. If your company already uses AWSsome, enter your work email. AWSsome finds your workspace, signs you in the way you sign in today, and connects HubSpot. If your email is in more than one workspace, you pick one. If your company has no AWSsome account yet, you fill in a short form and our team follows up. Until your workspace is set up, the app stays not connected and no data is exchanged.

**Which permissions does AWSsome ask for in HubSpot?**
Required: read and write deals, read and write companies, read contacts, read and create deal properties, read company properties, and read deal owners. Optional: read sales emails. AWSsome needs to write companies to add the company when it creates a deal from an AWS opportunity. "Help me improve the score" reads the deal's emails only if you grant the email permission. When a Super Admin approves the app, HubSpot shows the required and optional permissions, and only the optional ones can be turned off.

**Can I connect more than one HubSpot account?**
No. Each AWSsome workspace connects one HubSpot account (portal).

**How many pipelines can I sync?**
Up to 3. Each pipeline has its own stage mapping. Field mapping is one set for your whole HubSpot account. 

:::hint{type="info"}
Soon we're going to support up to 4 pipelines
:::

**We don't use HubSpot. Can we close the Connect HubSpot step?**
Yes. On the Connect HubSpot step, click "I don't use HubSpot". The step shows as Not applicable for everyone in your company, and the HubSpot reminder emails stop. Click Undo to bring it back.

## Syncing Deals

**Which deals does AWSsome pull?**
After setup, AWSsome pulls deals automatically from the pipelines you mapped. It pulls a deal when the deal's HubSpot stage maps to Prospect, Qualified, Technical Validation, Business Validation or Committed. It does not pull deals in stages mapped to Launched or Closed Lost, because AWS does not take opportunities that are already launched or lost. Your queue filters do not change which deals are pulled.

**How quickly do changes sync?**
HubSpot tells AWSsome right away when a deal is created or deleted, or when its name, amount, stage or close date changes. Once every 24 hours, AWSsome also checks your pipelines again to catch anything missed. AWS Partner Central sends real-time events when an opportunity changes. When the deal's status changes in AWSsome, AWSsome updates the HubSpot deal.

**Which HubSpot data does AWSsome read?**
The deal's core fields (name, amount, stage, close date, pipeline, owner, currency), the HubSpot properties you mapped or use in queue filters and columns, the deal's company (name, website, location, industry) and its contact (name, email). If you grant the email permission, AWSsome also reads the deal's emails for "Help me improve the score".

**Does AWSsome change my HubSpot data?**
AWSsome writes its own deal fields. It also moves the stage of a deal you submitted to AWS when the AWS stage changes. When you accept an opportunity that AWS shares, it creates one deal, finds or creates its company, and keeps that deal's name, amount and close date in line with AWS. AWSsome only reads your contacts.

## Submitting deals to AWS

**Who submits deals to AWS?**
Your own team, usually RevOps or partner managers, from the HubSpot queue in AWSsome. Deals are not submitted from HubSpot. Nothing is sent to AWS until someone on your team approves it.

**Which fields does AWS need?**
Before you submit, a deal needs a deal name, the customer company name, an amount above 0, a close date in the future, the customer country, and a postal code unless the country has no postal codes. AWS also requires the customer website and industry. AWS takes the industry only from its own list of values, so check it in the approve window. The deal needs a customer business problem of 20 to 2,000 characters and at least one solution. AWSsome fills in the solution and AWS products for you.

**Why can't I submit a deal?**
A deal with no amount, an amount of 0 or no deal name shows a Can't submit badge in the queue, and Submit stays off. Fix the deal in HubSpot, then refresh the queue. If AWSsome finds another problem when you submit, it shows each error next to its field. A close date in the past does not block you: the approve window moves it to tomorrow.

**What happens if a submission fails?**
If the deal fails AWSsome's checks, it goes back to Pending, so you can fix it and submit again. If AWS refuses a deal that passed the checks, the deal shows as Failed, and you can retry without a new review.

**What currency should my deals use?**
We recommend USD. AWSsome sends the deal value to AWS in USD and does not convert other currencies, so a deal in another currency is sent with its number unchanged. AWS accepts USD and EUR, but AWSsome sends USD today. AWSsome sends AWS an expected monthly AWS spend of 10% of the HubSpot amount, shown as Est. AWS MRR (monthly recurring revenue) in the approve window.

**What does AWS do after I submit?**
AWS reviews the deal. While the deal is Submitted or In Review, nobody can change it. AWS then approves it, rejects it, or sets it to Action Required. Action Required means AWS asks for fixes before it approves the deal. You can then change only the customer address, website, target close date, expected spend, business problem and partner opportunity ID, and the deal goes back into review. A rejected opportunity is read-only in AWS, so nobody can change it or submit it again. On the HubSpot card, Revise and resubmit in AWSsome opens the deal in AWSsome.

**How long does AWS take to review a deal?**
Usually up to 24h

**Can I edit a deal after AWS approves it?**
Yes, with limits. After approval, AWS does not accept changes to the deal title, the customer country, postal code, industry and website, the customer business problem, or the partner opportunity ID. If they change in HubSpot, the AWS record keeps the approved values. Before you submit, the values in HubSpot count. After you submit, the values in the AWS opportunity count, and stages still sync both ways.

## Deal Registration

**How does a HubSpot deal become an AWS opportunity?**

1. **Pulled** — the deal meets your criteria and appears in the AWSsome deal queue as *Pending Review*.
2. **Reviewed** — your team reviews the deal, adds the co-sell narrative (the "customer problem" AWS requires), selects the solution, and marks it *Ready*.
3. **Submitted** — AWSsome re-fetches the latest deal data from HubSpot and submits the opportunity to AWS Partner Central. The HubSpot deal is tagged with its submission status.
4. **In review with AWS** — AWS reviews the opportunity. Status updates (Approved, Action Required, Rejected) flow back into AWSsome and onto the HubSpot deal record.

Nothing is ever sent to AWS without a human on your team approving it first.

**What fields are required to submit a deal?**
Required: deal title, company name, amount, close date, and customer country. Recommended for better AWS matching: customer problem narrative, industry, postal code, and customer website. You choose which HubSpot properties feed these fields during setup.

**Who owns the deal data after submission?**
Before submission, HubSpot is the source of truth — edits to the deal in HubSpot flow into AWSsome. Once a deal is submitted to AWS, ownership flips: the AWS opportunity becomes authoritative, and AWSsome pushes AWS-side updates (stage, status, insights) back into HubSpot rather than the other way around. Stage changes your reps make in HubSpot still sync forward to AWS in real time.

**Can I edit a deal after AWS approves it?**
Some fields become permanent once AWS approves the opportunity — including the title, company name, customer problem, and customer website. If those change in HubSpot after approval, AWSsome flags the deal so your team can see the divergence, but the AWS record keeps the approved values.

**What currency should my deals use?**
AWS Partner Central accepts USD only. Deals in other currencies are submitted with their numeric amount as-is — there is no automatic currency conversion — so we recommend keeping synced pipelines in USD.

**What happens if a submission fails?**
The deal is marked *Submission Failed* in your AWSsome queue with the error details, and your team can fix the issue and retry. Nothing is lost.

## Stage Sync

**How do stages sync?**
After a deal is submitted, both ways. When a rep moves the deal in HubSpot, AWSsome moves the AWS opportunity to the mapped AWS stage. When AWS changes the stage, AWSsome moves the HubSpot deal to the mapped HubSpot stage. If AWS moves the deal to a stage you mapped to None, the HubSpot deal keeps its stage and no error shows.

**What if a deal is marked Closed Lost in HubSpot?**
AWSsome closes the AWS opportunity as Closed Lost. If AWS is still reviewing it, AWSsome waits until the review ends, because AWS blocks all changes during review. If the deal is reopened in HubSpot before then, the close is cancelled.

**What if I delete a deal in HubSpot?**
A deal you have not submitted leaves the queue. A submitted deal stays open in AWS. If it is no longer active, close it in AWSsome as Closed Lost.

## Deals from AWS Partner Central

**I registered deals in AWS Partner Central before I connected HubSpot. What do I do?**
AWSsome does not match them for you, because it does not guess which two records are the same deal. Link each pair by hand, from the queue or from the opportunity (see Guide 4). A link cannot be undone from the screen, so check the pair before you link.

**Does accepting an opportunity from AWS create a HubSpot deal?**
Yes. When you accept an opportunity that AWS shares, AWS creates the opportunity in your Partner Central account, and AWSsome creates one deal in your HubSpot (see Guide 6).

## In HubSpot

**What do my reps see in HubSpot?**
The AWSsome Deal Context card on each deal, once an admin adds it to the deal record (see Guide 5). AWSsome also keeps 17 deal fields up to date, including the visible AWS Engagement Level field. You can use these fields in views, lists, reports and workflows like any other deal property. The AWS Shared field no longer updates. If a workflow uses it, switch it to the Awssome Status field.

**Do reps need an AWSsome account?**
No. The card works for reps without an AWSsome account. When a rep clicks Open in AWSsome on the card and your HubSpot is connected, AWSsome signs the rep in, creates their account and opens the deal. If HubSpot is not connected, the rep sees a message to ask an admin to connect it.

**When does the card show AWS's score?**
Once AWS approves the deal. The score runs from 0 to 100, with a trend of Improving, Declining or No Change.

## Security and your account

**How is my HubSpot data secured?**
The connection uses HubSpot's standard OAuth sign-in, so AWSsome never sees or stores your HubSpot password. Access tokens are encrypted at rest and refreshed automatically. HubSpot notifications are verified before AWSsome processes them. Each customer's data is stored in its own database.

**Do I need to reconnect HubSpot?**
Only if you installed before the new permissions. Those installations must reconnect once to grant them. New installations do not. Use Re-authorize on the Integrations page. You do not need to disconnect, and your pipelines, mappings and setup stay as they are. Until you re-authorize, the connection keeps working, but deals created from AWS opportunities are created without their company.

**What if my connection expires?**
AWSsome refreshes access in the background, so this is rare. If HubSpot revokes access, for example because the user who connected it is deactivated, the Integrations page shows the connection as expired, and syncing pauses until you reconnect.

**What happens when I disconnect?**
Syncing stops and AWSsome removes its HubSpot connection. Deals already submitted to AWS are kept. Your mappings, filters and column choices are removed, so reconnecting starts the setup wizard again. Opportunities already in AWS Partner Central stay active.