HubSpot Integration FAQ

getting started what does the hubspot integration do? it connects your hubspot crm to awssome so your sales pipeline and aws co sell motion stay in sync concretely deals in your hubspot pipeline that meet your criteria are automatically pulled into a review queue in awssome after your team reviews and enriches a deal, awssome submits it to aws partner central as a co sell opportunity — no manual re entry in partner central once submitted, deal stages stay in sync in both directions move the deal in hubspot and the aws opportunity follows; when aws updates the opportunity, the hubspot deal stage updates too awssome writes status fields back onto your hubspot deal records, so your reps can see aws co sell status without leaving hubspot how do i connect hubspot to awssome? in awssome, go to integrations and click connect hubspot you're redirected to hubspot to authorize the connection (standard oauth — you log in with your hubspot account; awssome never sees your hubspot password) back in awssome, complete the setup wizard select the hubspot pipeline to sync, map your pipeline stages to aws opportunity stages, and map your deal fields to aws opportunity fields once setup is complete, awssome runs a first sync of your pipeline and starts listening for deal changes in real time what do i need before connecting? an active awssome account with publisher access, linked to aws partner central a hubspot account where you can grant app permissions for deals, companies, and contacts (admin or super admin rights are typically required to install apps) a paid hubspot tier that supports custom deal properties (sales hub starter or above) what permissions does awssome request in hubspot? read and write access to deals, read access to companies and contacts, and access to deal property schemas (so awssome can create its status fields on your deal records) awssome does not request access to emails, tickets, marketing data, or any other hubspot objects can i connect more than one hubspot account? no — one hubspot account (portal) per awssome workspace can i sync more than one pipeline? no — you select a single pipeline during setup if you change the selected pipeline later, your stage mappings are reset and you'll need to map the new pipeline's stages before syncing resumes syncing deals which deals get pulled from hubspot? a deal enters the awssome review queue when it belongs to the pipeline you selected during setup and sits in a stage mapped to an active aws stage (prospect through committed) deals mapped to launched or closed lost stages are not pulled — those are terminal stages in aws partner central every pulled deal is then automatically classified as good fit or not a fit for aws co sell, based on rules like minimum deal amount (default $25,000, configurable) and close date within a configurable horizon (default 180 days of today) deals that don't qualify aren't dropped — they stay visible with an aws fit status of "not a fit" and the specific reasons listed in aws fit reasons , both written back to the hubspot deal record if the deal later changes (say the amount is updated), the fit status updates too how quickly do changes sync? two mechanisms work together real time hubspot notifies awssome the moment a deal is created, deleted, or has its name, amount, stage, or close date changed daily sweep once every 24 hours, awssome re scans your pipeline to catch anything missed and reconcile deletions what deal data does awssome read? the deal's core fields (name, amount, stage, close date, pipeline, owner, currency), any custom deal properties you mapped during setup, plus basic details from the deal's first associated company (name, website, location, industry) and first associated contact (name, email) this data is used to build the aws opportunity does awssome change my hubspot data? awssome writes only to its own custom properties on deal records (all prefixed "aws" — see what do my reps see in hubspot? below) and updates the deal stage when the aws side of a submitted opportunity changes it never creates, edits, or deletes your contacts or companies, and never modifies your own deal fields — with the single exception of deal stage on deals you've submitted to aws does the integration create new hubspot deals from aws opportunities? no new opportunities flow one way hubspot → aws opportunities created directly in partner central are not pushed into hubspot as new deals for deals that originated in hubspot and were submitted, stage updates do flow back from aws deal registration how does a hubspot deal become an aws opportunity? pulled — the deal meets your criteria and appears in the awssome deal queue as pending review reviewed — your team reviews the deal, adds the co sell narrative (the "customer problem" aws requires), selects the solution, and marks it ready 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 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 does stage syncing work after submission? both directions, automatically hubspot → aws when a rep moves a submitted deal to a new stage, awssome updates the aws opportunity to the mapped stage aws → hubspot when the opportunity's stage changes on the aws side, awssome moves the hubspot deal to the mapped stage stages you mapped as "not applicable" during setup are ignored — moving a deal into one of those stages doesn't touch the aws opportunity what if a deal is marked closed lost in hubspot? awssome closes the aws opportunity as lost if aws hasn't finished reviewing the opportunity yet, awssome remembers the intent and closes it automatically as soon as aws approves it — you don't need to do anything if the deal is reopened in hubspot before that happens, the pending closure is cancelled what if the deal changes in hubspot and in aws at the same time? awssome applies safeguards opportunities already launched or closed lost on the aws side are never overwritten by hubspot changes, and while an aws side update is still being pushed to hubspot, conflicting hubspot changes are held back if a sync can't complete, the deal is flagged in your queue so your team sees the divergence instead of silently losing data what if i delete a deal in hubspot? deals not yet submitted are removed from the awssome queue if the deal was already submitted to aws, the aws opportunity stays open — deleting a crm record doesn't cancel a co sell engagement — and your team should close it in awssome if it's no longer active visibility in hubspot what do my reps see in hubspot? awssome creates a set of read only deal properties in your portal and keeps them updated as the deal moves through the co sell flow co sell status awssome status — where the deal sits in the flow (pending review, ready, submitted, in review, approved, action required, and so on) aws status — aws partner central's review status for the opportunity aws shared — whether the deal has been shared with aws aws fit status / aws fit reasons — whether the deal qualifies for aws co sell, and why not if it doesn't aws opportunity intelligence (populated as aws shares it, typically after approval) aws opportunity quality score (0–100), quality trend , and quality reasoning — aws's assessment of the opportunity and specific guidance on how to strengthen it aws recommendation and aws next best action — aws's suggested actions for the deal aws engagement score — aws's engagement rating aws account manager name and aws account manager email — the aws seller assigned to the opportunity, so your rep can start the co sell conversation directly housekeeping aws deal url — deep link to the deal in awssome aws last synced at — when awssome last updated the record you can surface all of these in hubspot views, lists, reports, and workflows like any other deal property a few additional properties (buyer intelligence signals, ai drafted intro email, recommended next step) exist behind the scenes to power the awssome sidebar card and are hidden from the deal panel by default security & account management how is my hubspot data secured? the connection uses hubspot's standard oauth — awssome never sees or stores your hubspot password access tokens are encrypted at rest (aes 256) and refreshed automatically incoming hubspot notifications are cryptographically verified before processing each customer's data is stored in an isolated, per customer database what happens if my connection expires or breaks? awssome refreshes tokens automatically in the background, so this is rare if hubspot revokes access (for example, the authorizing user is deactivated), the connection shows as expired in your integrations page and syncing pauses until you reconnect no data is lost while disconnected what happens when i disconnect? syncing stops immediately and awssome revokes its access token with hubspot field and stage mappings and unsubmitted queued deals are removed records of deals already submitted to aws are kept for audit and continuity if you reconnect later, awssome reconciles what happened while disconnected — including deals that closed in hubspot in the meantime does disconnecting cancel my aws opportunities? no opportunities already submitted to aws partner central remain active disconnecting only stops the sync between hubspot and awssome